Skip to content
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

Keep older nodejs 5.x versions available? #192

Closed
msabramo opened this issue Dec 9, 2015 · 3 comments
Closed

Keep older nodejs 5.x versions available? #192

msabramo opened this issue Dec 9, 2015 · 3 comments

Comments

@msabramo
Copy link

msabramo commented Dec 9, 2015

A few days ago we were pinning to nodejs=5.0.* and our playbooks for spinning up VMs were working. Then NodeJS 5.1.1 was released on 2015-12-04 (5 days ago!) and our stuff broke -- it seems that when 5.1.1 was released all of the 5.0.* versions became unavailable?

So just yesterday someone changed it from nodejs=5.0.* to nodejs=5.1.* and everything was working again.

Today it's broken again. I'm presuming this is because NodeJS 5.2 was released today (2015-12-09) and the all of the 5.1.* versions became unavailable?

What is the process for pinning to some known stable version of NodeJS? I could change it to 5.* but that seems risky to grab whatever the latest 5.x version of NodeJS is, as we have not tested our apps with these newer versions. I think I'd feel more comfortable pinning to a 5.1.2 or at least 5.1.*, but perhaps this is not possible?

What is the recommended way to get a stable version of NodeJS that won't keep going away as we'd prefer for all of our VMs spun up over time to have the same version?

Are the NodeSource repos intended only for development and not for production use? Should we use the Ubuntu repos instead of the NodeSource ones to get the stability we want?

@retrohacker
Copy link
Contributor

Hey @msabramo. @chrislea may have a better solution than I for pinning to a version, but these repositories are certainly maintained with production use in mind.

The .deb files are still on the server: https://deb.nodesource.com/node_5.x/pool/main/n/nodejs/

For my Docker images I am pinning to specific versions by using dpkg -i. An example can be found here: https://github.com/nodesource/docker-node/tree/master/debian/jessie/node/5.1.1

Unsure what the proper steps are to get the same behaviour out of apt. Perhaps @rvagg or @chrislea can chime in?

@msabramo
Copy link
Author

msabramo commented Dec 9, 2015

Thanks, @wblankenship! Ah you're right, the .deb files are still there. I wonder if they are just not being included in the apt index files...?

I noticed that https://deb.nodesource.com/node_5.x/dists/trusty/main/binary-amd64/Packages only references the 5.2.0-1nodesource1~trusty1 version...

@retrohacker
Copy link
Contributor

This is a duplicate of #33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants