The installation script doesn't work correctly on Ubuntu 16.04 LTS. When the user intends to install v6, v4 is actually installed. #358
Comments
|
Looking at that forum post, there's no bug to report here. It just says "the installer script didn't do what it's supposed to do". If the installer script doesn't run, then you'll get Node v4.2.6 because that's what's in the mainline Ubuntu repositories. If the installer script is failing for you in some way, please re-open this issue and provide the exact command you are using to run the script as well as any console output so we can try and see what's going on. Thanks. |
|
I don't know how "there is no bug to report here". The reproduction steps are clear: Just run on any Ubuntu 16.04 LTS and you get node 4.26 installed instead of v6. The console doesn't output any error or whatsoever, the output suggests everything is normal but eventually v4 gets installed. The output of the script: Is that not enough? What else are users supposed to provide here. Of course the answer just says "the installer script didn't do what it's supposed to do", because it reports everything is normal and then boom, nothing works! Why doesn't somebody from the nodesource team actually try it out on Ubuntu 16.04 LTS and see if they can reproduce the issue as described instead of just closing the issue without even looking at it? The question is upvoted 17 times on StackExchange. I and the OP are certainly not the only ones impacted by it. It's not like 17 people just pop out of nowhere upvoting posts for fun. This is a quite insidious issue, since no error message is ever shown, a user might well expect Node v6 to be installed, only to face a load of issues later on. And I don't believe users of Ubuntu 16.04 LTS to be exactly a minority either. |
|
I can't reopen the issue myself. Please look at the new issue I created. |
|
Okay, we're sorry you are running into that. We have tested this installer extensively on Ubuntu 16.04 (I am typing this from my home desktop, which is running Ubuntu 16.04 for example), and we obviously didn't see this or else we wouldn't have shipped anything. I need to see the complete console output from the installer script. Also, if you could download it directly to your machine and run it as and attach the complete output here also that should help as a starting point. Re-opening as requested. |
|
Also as @mweagle noted, if after the script runs, can you also let us know what the output of: as well as are? Thanks. |
|
I had this problem on Ubuntu trusty, 14.04.4 LTS, on Joyent. Then I recalled docs that said there is some conflict with the name node on ubuntu. Also, note the install locations are diffent Also, npm is installed but in a different place, so: |
|
Okay, you clearly have more than one thing installed. Please clear out all previous node or npm packages. You can see what you have with: $ dpkg -l | grep -E 'nodejs|npm'After you remove everything, please remove the NodeSource apt list entry with $ sudo rm -fv /etc/apt/sources.list.d/nodesource*Then, you need to additionally make sure you've uninstalled any other non-packaged versions of node. The command: $ which nodeshould return nothing. Then run the installer script again. |
|
I tried removing everything, then: I saved setup_6.x locally, then ran:
The output seems to show a 404: |
|
That is a problem in your I am immediately suspicious because the PPA pathname indicates Ubuntu Trusty, but it's looking for a Ubuntu Xenial repository. But, whatever is happening here, it is happening before |
|
@chrislea |
|
@Rim-777 In my case, it was a problem with the package manager. Fixed it by removing broken PPAs: https://stackoverflow.com/questions/48691220/error-executing-command-exiting-error-upon-installation-of-nodejs |
As documented at http://askubuntu.com/questions/786272/why-does-installing-node-6-x-on-ubuntu-16-04-actually-install-node-4-2-6, apparently there's some error in node installation script and when the user intends to install Node v6 on Ubuntu 16.04 LTS, v4 is actually installed. One has to manually add the NodeJS entry in
sources.list.dfor the installation to work.Although that question on StackExchange was asked in June, I'm surprised to still encounter the same error, three months later. Seems that nobody filed a bug report.
The text was updated successfully, but these errors were encountered: