-
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
Node.js v0.12 distribution #63
Comments
Postgres used to do it like this for debian:
|
Any chance we can at least get 0.12 on node-devel? |
Hi all. We have 0.12.0 packages built! They are "public" in the sense that you can reach them via the open interwebz, but we haven't made any official announcements yet because we'd love it if we could get a little sanity checking from the community first. Assuming you are set up with the mainline NodeSource repository (last published version was 0.10.36) then the following command should switch you over to the 0.12.x repository.
After that a familiar
should install 0.12.0 for you. If people could please take it out and kick the tires a bit I'd really appreciate it. Please let us know here if you find anything. Assuming it all looks good, we'll make an official announcement. Thanks very much in advance! |
Got 0.12 running under utopic without any hiccups; taking it for a spin to ensure all is well. Edit: gulp is not happy, complaining about being unable to find module 'app.js'. Going to have to dig to see if this is 0.12 related, gulp related, or me being an idiot related. Aaaand it was related to a breaking change in gulp-express, nothing to do with node. So, all good. |
@chrislea Just curious, are 0.12.0 built packages available also for EL? |
@paambaati We're working on EL builds. Getting things to work for EL 5 is just an exercise in awfulness, but I'm giving it as much time / attention as I can. |
why no add update for version 0.12 in the 'normal' ubuntu repositoriy ? , the release is 'stable' https://github.com/joyent/node/releases/tag/v0.12.0. |
Just wondering whenever this'll land for me via: Certain vendors are seemingly bypassing |
@antwan1986 That's because 0.11 was the development version for 0.12. Even numbers are the production ones. |
Pick one. We're about to announce this "officially" including more details about what's there and the rationale for the way we've done it, but you should be able to start using it now. |
What about RPM packages? |
Coming, see https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories The .debs for newer distros were the lowest-hanging fruit so we picked them off first, keep an eye on this repo for more news. |
May you add armhf binaries to https://deb.nodesource.com/node_0.12 ? |
@samkrew yes, it'll be coming, just like older Linux distros it's a bit of trickiness we're pushing down the road a little way. Please keep an eye on this repo for more news about it. |
Sorry about that @samkrew, the ARM builds for 0.12.0 should be in the repo now. |
Will the node_0.12 build be updated regularly? It looks like it is still on v0.12.0. |
Yes, 0.12.1 should be in the repo in a few hours. |
0.12.0 upgrade smooth for me. Great work :) |
Any news about RPMs for EL? |
They should be up today. |
Is 0.12.1 up for deb? My node version still reports 0.12.0.
|
How do I get RPMs for 0.12? |
@chrislea still can't find Node 0.12.x on yum:
|
Just wondering if there is any update on the ETA for EL6 RPMs? |
Any news on this? |
+1 to @jamiemcconnell 's question. EDIT: It looks like they may be here. https://rpm.nodesource.com/pub_0.12/el/6/x86_64/ |
Hi there, any news regarding RPMS for EL7 ? |
Has anyone tried the packages that @owenallenaz pointed out? |
The README @ https://github.com/nodesource/distributions has updated instructions for io.js and 0.12 on Debian / Ubuntu, although support is still limited on older systems so don't expect full coverage (build chain dramas make this really hard). RPMs are being built for Node 0.12 for Fedora and EL6 and EL7 but you'll have to download them manually from http://rpm.nodesource.com/pub_0.12/ as the setup procedure is still being worked on and we need some people to test the RPMs. io.js v2.x RPMs are also available for Fedora and EL7 at https://rpm.nodesource.com/pub_iojs_2.x/ - we'd love feedback on these RPMs if you're using them. |
I just installed the Node 12 on Centos 6 running the following steps: # remove old version, replace with your specific needs
sudo yum remove nodejs
# download the file
sudo curl -O https://rpm.nodesource.com/pub_0.12/el/6/x86_64/nodejs-0.12.7-1nodesource.el6.x86_64.rpm
# install the rpm
sudo rpm -Uvh nodejs-0.12.7-1nodesource.el6.x86_64.rpm
# remove downloaded file
sudo rm nodejs-0.12.7-1nodesource.el6.x86_64.rpm
# verify node works
node -v
# v0.12.7
# verify npm works
npm -v
# 2.11.3 So far everything appears to be running fine, will report back if I have an issue. |
Node.js v0.12 v0.10 segfault on raspberry B/B+ running Raspbian 7 Wheezy: |
@empierre: ARM is not an officially supported architecture for v0.10 or v0.12, also if you're using any |
@rvagg looks like it works from the nodejs site. I guess that for many people armv6 should not be present on nodesource wich is so well referenced on google... that would save people lot of time ! thanks for the link ! |
@empierre good point, I don't see a reference to ARMv6 or Pi on our documentation, I'll try and get around to fixing that (although a PR would be welcome if you have the time!) |
0.12 has been released for quite some time. Closing this issue as stale. |
Per @chrislea's previous experience with the v0.8 transition to v0.10 breaking a large number of builds, we're working on a strategy to make sure the same thing does not happen with the v0.12 release.
Given the number of issues the io.js team has encountered with native modules, there's a high likelihood that this will occur in v0.12.
@chris-prince has some useful suggestions in #33.
The text was updated successfully, but these errors were encountered: