Node.js Conflicts: /sbin/Node vs /usr/bin/Node

Asked

Viewed 113 times

0

Good morning, everyone ! I would like someone to exclaim very well this conflict that arises in the installation of the nodejs ?

Thanks!

javascript linux node.js raspberry-pi debian

  • experiemente http://askubuntu.com/questions/235655/node-js-conflicts-sbin-node-vs-usr-bin-node

  • you want to install as /sbin/Node or /usr/bin/Node ?

  • @Fábioarsenium there is a conflict between these two woes, I just need to know what it really is. What is the reason for this conflict and how to resolve ? I am doing a job and I need to report this error. THANK YOU !

  • @Miguel would be better a reference in French, I have serious weaknesses in English ... !! But however thank you for your support... GRATEFUL !

  • They basically say the solution is sudo apt-get install nodejs-legacy

  • Both debian and Ubuntu nodejs force the use of the nodejs-legacy package

  • @Miguel much more than the solution what matters most is the copressao of the "bug" ! Type what happened to install "nodejs-legacy"? I only intend to understand this conflict between these two repertoires there ! GRATEFUL FOR INTECAO .

  • Thank you @Fábioarsênio ! But why ? What is the reason for this ?

  • Thank you very much for the attention @Fábioarsênio ! Look I believe I am not making feel my question, in fact the problem has already been solved, I would like to know however to what is the conflict between these two repertoires ? Why does nodejs require the path to the binary to be usr/bin/Node and not usr/bin/nodejs ? I am preparing a report and I need to explain not simply the resolution of the problem, but also the cause !

Show 4 more comments

1 answer

0

To package node-js legacy contains a symlink for the Node-js code, which requires the path for the torque is usr/bin/Node and not usr/bin/nodejs as it is in the Debian. To nay installation of legacy nodejs package can generate these conflicts between paths, either as in the example I gave or even between /sbin/Node and /usr/bin/Node

Although not part of what you want to do, you can try to test the installation of this package in a virtual machine just to see if it still generates that same conflict.

  • Thank you so much for the attention @Fábioarsênio ! Look I believe I am not making feel my question, in fact the problem has already been solved, I would like to know however to what is the conflict between these two repertoires ? Why does nodejs require the path to the binary to be usr/bin/Node and not usr/bin/nodejs ? I am preparing a report and I need to explain not simply the resolution of the problem, but also the cause !

  • I have been searching and the latest version of nodejs requires the path to be such /usr/bin/Node , so creating this conflict if this legacy package is not installed, the legacy package will force the path update from an older version of nodejs to the newer one, also forcing the path change to binary. All this through the symlink that the package contains

  • If it becomes easier I can add this last piece of information to the answer! @Andrépka

  • Thanks @Fabio ! If you still have some information you can add... MERCI !

Browser other questions tagged javascript linux node.js raspberry-pi debian

You are not signed in. Login or sign up in order to post.