-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nodejs automatically updated to 0.11.15 in Ubuntu utopic-amd64 as of 2015-01-29 #60
Comments
Hi. It seems for utopic it was built the unstable version and I have the same problem. |
Okay, thanks! |
Just for the record
|
+1 |
This broke our deploys. It's especially frustrating since version-stability was kind of the whole reason for installing with NodeSource. The unstable nodejs version will fail for anyone trying to install node-sass (250k+ downloads last month) and likely other modules with bundled binaries. |
So no, that should not be happening. The 0.10.x builds and the 0.11.x builds are in different repositories. Can somebody show me the output of:
from an affected machine? |
I don't have it here but if you browse the repo files you will see that for Ubuntu 14.10 unicorn, it was built only the unstable version. Because it's the highest it's the one we get upgraded to. |
Sorry, utopic, not unicorn and see check the directory, https://deb.nodesource.com/node/pool/main/n/nodejs/ |
@chrislea This is what I got from a freshly deployed Ubuntu 14.10 x64 VPS just now after running the NodeSource install script:
|
Thanks @joemaller. So first thing's first, which is my apologies that this happened to being with. It was our (my) error, not anything anyone on this thread did wrong. I'm still not exactly sure how this got messed up as it's a fairly automated process, but I'll review things and see if I can clean things up better. So second thing, thanks to everybody for reporting this so I could get it fixed. The 0.11.x build for utopic has been removed from the repo and 0.10.36 has been installed properly. You should be able to trust that the NodeSource repos are going to work as expected. Unfortunately, if you got hit by this, you will have to get rid of the 0.11.x build first before you can get back to "situation normal". I believe the following commands, as root, should do the trick for you:
If there are still issues please report them here. I will leave this open until I get some verification that things are okay again. |
👍 |
@chrislea Looks like we're all good again, thank you! Here's the
|
Thanks for the report. Closing this down. |
Hello. Is this expected? Is there a way to revert to 0.10.x?
The text was updated successfully, but these errors were encountered: