Support for Ubuntu Utopic (14.10) about distributions HOT 24 CLOSED

When I executed the second command, happen the bellow error:

root@tbmachado-Vostro-3560:~/git/hu-b2b# curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
gpg: no valid OpenPGP data found.

The version of my ubuntu is:

Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty

from distributions.

Can you try this again please and let me know if it's working for you or not? We apparently had a problem with the key availability for a short period.

Also, since you're on trusty you don't need to do the full thing I listed above which are for Utopic, the next version of Ubuntu (14.10) which is currently in Beta. Just do the normal install:

curl -sL https://deb.nodesource.com/setup | sudo bash -

from distributions.

Thank you very much, This fixed my issues & was quite easier from other docs online

"curl -sL https://deb.nodesource.com/setup | sudo bash -"

I followed first steps, and failed to pass the first test, this is what i got;

Running test ...

• npm test

[email protected] test /_test-node-install
npm start; node test.js

[email protected] start /_test-node-install
node server.js &

sh: 1: node: not found
sh: 1: node: not found
npm ERR! weird error 127
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! not ok code 0
Error executing command

Cleaning up ...

After re-installing with >" curl -sL https://deb.nodesource.com/setup | sudo bash - "
everything was solved. Thanks rvagg, save me time!!!

from distributions.

@rvagg Thank you, worked perfectly on Ubuntu 14.10, which will be officially launched this week.

from distributions.

14.10 has now been launched. Can we use this?

from distributions.

indeed you can, debs are in place, the setup script should just pick them up!

from distributions.

The PPA provided by Nodesource is still downloading the following version:

pires@orion:~$ node --version
v0.10.25

Although NodeJS' website states that v0.10.33 is the current version.
Any idea if this is going to be updated soon on the PPA? My company has a lot of projects relying on node modules that needs updating for new funcionalities, and the PPA you created has been saving a lot of work for us now, I don't want to make everyone drop it and install it manually...

Thanks in advance.

from distributions.

@viniciuspires perhaps you have an install conflict here somewhere? I don't believe the NodeSource repo even has binaries for v0.10.25 available for any distro so that shouldn't have come from us. Try doing an apt-get purge nodejs; apt-get purge nodejs-legacy; just in case, then run curl -sL https://deb.nodesource.com/setup | sudo bash - to run the setup again, then apt-get install nodejs to get it.

from distributions.

@rvagg When I curl the setup and pipe to bash, at the end of the operation I'm getting the message:

## Confirming "trusty" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node/dists/trusty/Release'

## Your distribution, identified as "trusty", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

On Ubuntu 14.04. When running sudo apt-get install nodejs again I still get:

pires@orion:~$ nodejs --version
v0.10.25

from distributions.

+1

from distributions.

dpkg -l | grep node - what shows up for this? you must have a conflicting package, or a conflicting binary install from somewhere else: which nodejs?

from distributions.

@rvagg Sorry it was my fault, i was using https://deb.nodesource.com/setup_dev instead of https://deb.nodesource.com/setup.

from distributions.

pires@orion:~$ dpkg -l | grep node
ii  nodejs                                                0.10.25~dfsg2-2ubuntu1                              i386         evented I/O for V8 javascript

pires@orion:~$ which node
/usr/bin/node

from distributions.

@viniciuspires that's not our package, I think that's the native Ubuntu one. Remove it and run our setup again via curl and then npm install nodejs.

from distributions.

Same message:

## Confirming "trusty" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node/dists/trusty/Release'

## Your distribution, identified as "trusty", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

:/

from distributions.

@viniciuspires are you behind a proxy? can you curl -sL https://deb.nodesource.com/node/dists/trusty/Release from that server and get a response?

from distributions.

Yes, I am. Sorry, I forgot to mention that.

pires@orion:~$ curl -sL https://deb.nodesource.com/node/dists/trusty/Release
Origin: Node Source
Label: Node Source
Codename: trusty
Date: Fri, 31 Oct 2014 22:16:00 UTC
Architectures: i386 amd64 armhf
Components: main
Description: Apt Repository for Node.JS
MD5Sum:
 a13a8bb2462e11a500bc0407d9169f21 2247 main/binary-i386/Packages
 43467b95a9be88f0c5f4c2b639861e67 928 main/binary-i386/Packages.gz
 858bcc6f092bf9a62b95ec25133a16fc 114 main/binary-i386/Release
 2ab8ce08396b7d1e4d2da71522679022 2251 main/binary-amd64/Packages
 ec661c75a62254920e8e691182625b96 926 main/binary-amd64/Packages.gz
 ebcbc5a586d54ca7a0899d0cbc5cdab5 115 main/binary-amd64/Release
 f2ace78d773f5fd329a2b465e023c0d9 2251 main/binary-armhf/Packages
 7da0b2ecc723a871df6dc1be65aa388c 929 main/binary-armhf/Packages.gz
 721cd7a3a302487ca2b1dca9e74258c3 115 main/binary-armhf/Release
 92414a719a1c6f34a64d6bdeb1a13839 1326 main/source/Sources
 4008f929e58926626ffefc0c65f22000 678 main/source/Sources.gz
 c1ddc3434e3b1071bb4049689446e8a8 116 main/source/Release
SHA1:
 34e5364228dd7ec4108eacbb4e2e69610a29024d 2247 main/binary-i386/Packages
 c9df35ec63bd7d3e2955262790d8f2c56e61b1b6 928 main/binary-i386/Packages.gz
 babad9e9ef91e8e9f25072469cb3cacf37c1eeb2 114 main/binary-i386/Release
 41717e53912423cfdccded488ab2f45923a1a143 2251 main/binary-amd64/Packages
 b3fa941105826d2740d37f2829332a9038d6c69b 926 main/binary-amd64/Packages.gz
 034ed7854f4ef3fe3bba8a19c2a8e0a735312580 115 main/binary-amd64/Release
 ae76954268989aaa1122f350244b2e1e196abdbc 2251 main/binary-armhf/Packages
 ef68f7241af35dc81fb27166d1b2849b381779ba 929 main/binary-armhf/Packages.gz
 e1a4368c7c97d93c775eb481da4f975ff00ca98b 115 main/binary-armhf/Release
 cc678d15784410fb6c432ea975d33613afa5b7a7 1326 main/source/Sources
 c889ad026bef665ac097ca0b8fe220caa7803cb5 678 main/source/Sources.gz
 a722052b58db6ccc3213b13f5c854cd7a7f4ab4d 116 main/source/Release
SHA256:
 fc89c10cd927b048decc2d6ea8c02e10ed38374ee122c7ac756353d1c7740bbb 2247 main/binary-i386/Packages
 270e5d547fbe431677cefe9225931e5fffac2ee3646b7255cfa1fabf48887161 928 main/binary-i386/Packages.gz
 f7cb044aad412645efd0863f196d77112315034f96097fa4649dfeaffc975882 114 main/binary-i386/Release
 a089a9a2a50f02455d577fc53e67cd17c799f74dd9127d243b1e806085b399d5 2251 main/binary-amd64/Packages
 7bfe6ef365bc2c32efe313a32b26558e0da08f3e43f0b8293fdc2ce2ec5bde55 926 main/binary-amd64/Packages.gz
 94b5ac1474328b250dda1f9c2d3c6faef49be577e2d040a3bf82539416b7e590 115 main/binary-amd64/Release
 fb17bad2200d04ef18d75df6aeccf2940a08b920ed38c4eef514c45660f80c4c 2251 main/binary-armhf/Packages
 bbbc3dfb95130383f45c009afa22cc7244f12249f7dd0697c2f89a34a9b70b01 929 main/binary-armhf/Packages.gz
 f506560ef59c0cfe16e7c22f6cfd5e97d1e522878b9713eb9e64b201f26caed0 115 main/binary-armhf/Release
 ca7f47374b1e735ab27dadd51f057621f9162bd9a1f27f1c3a80f1ad28f9148d 1326 main/source/Sources
 48685b1f539df376f43dac90c0c1380514db35617e779555bcbcbd8da6090007 678 main/source/Sources.gz
 d22c7052b7fed518c59760fc426ce1cccc44ec595a8d91aa544f3acd623f2297 116 main/source/Release

PS.: I get the same result in the browser.

from distributions.

right, I think this is about #20 and #22, we need to get that sorted still

from distributions.

@rvagg Ha! The problem was really the *_proxy variables that were being lost at sudo. Although, sudo -E solved the problem, after that:

pires@orion:~$ nodejs --version
v0.10.33

Suggestion: the install command at the documentation could change from
curl -sL https://deb.nodesource.com/setup | sudo bash - to
curl -sL https://deb.nodesource.com/setup | sudo -E bash -

Assuming that most companies have proxies and people tend to not remember that the environment variables won't be kept by sudo without the -E option.

Anyway, thanks a lot!

from distributions.

@rvagg

We won't be officially supporting Utopic until it's released by Canonical, towards the end of October.

Well, it is released for some time now, when will it be oficially supported (or the docs get updated)?

from distributions.

Apologies, I'll check if we need to update the docs, but builds for Utopic have been in the repo ever since it was released. You should be able to install it just as you would for Trusty or any other supported distro.

from distributions.

@chrislea Sorry for not being specific, see the revision comparison. It links to this issue; it's probably not nodesource's fault but you could have closed this issue nevertheless :)

from distributions.

https://github.com/nodesource/distributions still doesn't mention 14.10. Is it supported now? When I follow the installation steps at https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions, I end up with v10.0.25 because of the failures below. I'm not behind a proxy.

W: Failed to fetch https://deb.nodesource.com/node_5.x/dists/utopic/main/source/Sources  HttpError404

W: Failed to fetch https://deb.nodesource.com/node_5.x/dists/utopic/main/binary-amd64/Packages  HttpError404

W: Failed to fetch https://deb.nodesource.com/node_5.x/dists/utopic/main/binary-i386/Packages  HttpError404

from distributions.

@dandv Ubuntu Utopic hit the end of it's supported release schedule in July of 2015 (see here). Once a distro stops being supported by Canonical, we can't support it either. Sorry!

from distributions.