nodesource / distributions Goto Github PK
View Code? Open in Web Editor NEWNodeSource Node.js Binary Distributions
Home Page: https://nodesource.com
License: MIT License
NodeSource Node.js Binary Distributions
Home Page: https://nodesource.com
License: MIT License
hi all ,
i am using debian testing 'jessie' and it seems don't support by nodesource team ,what should i do
?
curl -sL https://deb.nodesource.com/setup | bash -
hi,
can you help to add in
cloudlinux-release-6-6.6.0.x86_64 ?
its part of centos 6.6 / redhat linux equivalent.
thanks
Maybe I'm doing something wrong but can't get the lastest stable version 0.10.36! I really need it because the debugger is broken in 0.10.35...
With Linux Mint 17.1, shows "Your distribution, identified as "trusty", is not currently supported"
syamil@NADIA:~ > curl -sL https://deb.nodesource.com/setup | sudo bash -
## Populating apt-get cache...
+ apt-get update
Ign http://extra.linuxmint.com rebecca InRelease
Ign http://packages.linuxmint.com rebecca InRelease
Get:1 http://extra.linuxmint.com rebecca Release.gpg [198 B]
Ign http://archive.ubuntu.com trusty InRelease
Ign http://security.ubuntu.com trusty-security InRelease
Get:2 http://packages.linuxmint.com rebecca Release.gpg [198 B]
Get:3 http://extra.linuxmint.com rebecca Release [3.152 B]
Get:4 http://security.ubuntu.com trusty-security Release.gpg [933 B]
Get:5 http://packages.linuxmint.com rebecca Release [24,1 kB]
Ign http://archive.ubuntu.com trusty-updates InRelease
Get:6 http://extra.linuxmint.com rebecca/main amd64 Packages [7.902 B]
Get:7 http://security.ubuntu.com trusty-security Release [62,0 kB]
Get:8 http://extra.linuxmint.com rebecca/main i386 Packages [7.889 B]
Hit http://archive.ubuntu.com trusty Release.gpg
Get:9 http://packages.linuxmint.com rebecca/main amd64 Packages [32,2 kB]
Get:10 http://archive.ubuntu.com trusty-updates Release.gpg [933 B]
Get:11 http://security.ubuntu.com trusty-security/main amd64 Packages [196 kB]
Get:12 http://packages.linuxmint.com rebecca/upstream amd64 Packages [30,0 kB]
Hit http://archive.ubuntu.com trusty Release
Get:13 http://packages.linuxmint.com rebecca/import amd64 Packages [218 kB]
Get:14 http://archive.ubuntu.com trusty-updates Release [62,0 kB]
Get:15 http://security.ubuntu.com trusty-security/restricted amd64 Packages [8.875 B]
Get:16 http://security.ubuntu.com trusty-security/universe amd64 Packages [84,2 kB]
Get:17 http://security.ubuntu.com trusty-security/multiverse amd64 Packages [1.166 B]
Get:18 http://packages.linuxmint.com rebecca/main i386 Packages [31,5 kB]
Get:19 http://security.ubuntu.com trusty-security/main i386 Packages [187 kB]
Ign http://extra.linuxmint.com rebecca/main Translation-en_US
Hit http://archive.ubuntu.com trusty/main amd64 Packages
Get:20 http://packages.linuxmint.com rebecca/upstream i386 Packages [30,0 kB]
Ign http://extra.linuxmint.com rebecca/main Translation-en
Get:21 http://security.ubuntu.com trusty-security/restricted i386 Packages [8.846 B]
Hit http://archive.ubuntu.com trusty/restricted amd64 Packages
Get:22 http://security.ubuntu.com trusty-security/universe i386 Packages [84,2 kB]
Get:23 http://packages.linuxmint.com rebecca/import i386 Packages [219 kB]
Hit http://archive.ubuntu.com trusty/universe amd64 Packages
Get:24 http://security.ubuntu.com trusty-security/multiverse i386 Packages [1.412 B]
Hit http://security.ubuntu.com trusty-security/main Translation-en
Hit http://archive.ubuntu.com trusty/multiverse amd64 Packages
Hit http://security.ubuntu.com trusty-security/multiverse Translation-en
Hit http://archive.ubuntu.com trusty/main i386 Packages
Hit http://security.ubuntu.com trusty-security/restricted Translation-en
Hit http://security.ubuntu.com trusty-security/universe Translation-en
Hit http://archive.ubuntu.com trusty/restricted i386 Packages
Hit http://archive.ubuntu.com trusty/universe i386 Packages
Hit http://archive.ubuntu.com trusty/multiverse i386 Packages
Hit http://archive.ubuntu.com trusty/main Translation-en
Hit http://archive.ubuntu.com trusty/multiverse Translation-en
Hit http://archive.ubuntu.com trusty/restricted Translation-en
Hit http://archive.ubuntu.com trusty/universe Translation-en
Get:25 http://archive.ubuntu.com trusty-updates/main amd64 Packages [398 kB]
Get:26 http://archive.ubuntu.com trusty-updates/restricted amd64 Packages [8.875 B]
Ign http://packages.linuxmint.com rebecca/import Translation-en_US
Ign http://packages.linuxmint.com rebecca/import Translation-en
Ign http://packages.linuxmint.com rebecca/main Translation-en_US
Get:27 http://archive.ubuntu.com trusty-updates/universe amd64 Packages [239 kB]
Ign http://packages.linuxmint.com rebecca/main Translation-en
Ign http://packages.linuxmint.com rebecca/upstream Translation-en_US
Ign http://packages.linuxmint.com rebecca/upstream Translation-en
Get:28 http://archive.ubuntu.com trusty-updates/multiverse amd64 Packages [9.373 B]
Get:29 http://archive.ubuntu.com trusty-updates/main i386 Packages [390 kB]
Get:30 http://archive.ubuntu.com trusty-updates/restricted i386 Packages [8.846 B]
Get:31 http://archive.ubuntu.com trusty-updates/universe i386 Packages [240 kB]
Get:32 http://archive.ubuntu.com trusty-updates/multiverse i386 Packages [9.567 B]
Hit http://archive.ubuntu.com trusty-updates/main Translation-en
Hit http://archive.ubuntu.com trusty-updates/multiverse Translation-en
Hit http://archive.ubuntu.com trusty-updates/restricted Translation-en
Hit http://archive.ubuntu.com trusty-updates/universe Translation-en
Ign http://archive.ubuntu.com trusty/main Translation-en_US
Ign http://archive.ubuntu.com trusty/multiverse Translation-en_US
Ign http://archive.ubuntu.com trusty/restricted Translation-en_US
Ign http://archive.ubuntu.com trusty/universe Translation-en_US
Ign http://archive.canonical.com trusty InRelease
Hit http://archive.canonical.com trusty Release.gpg
Hit http://archive.canonical.com trusty Release
Hit http://archive.canonical.com trusty/partner amd64 Packages
Hit http://archive.canonical.com trusty/partner i386 Packages
Ign http://archive.canonical.com trusty/partner Translation-en
Fetched 2.606 kB in 2min 30s (17,4 kB/s)
Reading package lists... Done
## You seem to be using Linux Mint version rebecca.
## This maps to Ubuntu "trusty"... Adjusting for you...
## 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
syamil@NADIA:~ >
Tag @ceefour
## Confirming "fc21-x86_64" is supported...
+ curl -sLf -o /dev/null 'https://rpm.nodesource.com/pub/fc/21/x86_64/nodesource-release-fc21-1.noarch.rpm'
## Your distribution, identified as "fedora-release-21-0.16.noarch", 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
👎 :(
Just did this on Ubuntu 14.10:
$ curl -sL https://deb.nodesource.com/setup | sudo bash -
...
$ sudo apt-get install nodejs
...
$ npm -v
1.4.28
How come I do not have npm v2.x here?
$ sudo apt-cache policy nodejs
nodejs:
Installed: 0.10.33-2nodesource1~utopic1
Candidate: 0.10.33-2nodesource1~utopic1
Version table:
*** 0.10.33-2nodesource1~utopic1 0
500 https://deb.nodesource.com/node/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
0.10.25~dfsg2-2ubuntu1 0
500 http://nz.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
It would be helpful to mention which version of NodeJS (and/or IOJS) you've installed in this distros. I looked throughout the README and couldn't find anything.
I receive the following message when trying to install via "curl -kL https://rpm.nodesource.com/setup | bash -": "Your distribution, identified as "redhat-release-5Server-5.5.0.2", is not currently supported". What can be done to fix this? Is a newer version of rhel5 supported?
Thanks
curl -sL https://deb.nodesource.com/setup | sudo bash -
[sudo] password for gustavo:
More info about Elementary:
http://elementaryos.org/journal/freya-beta-1-available-for-developers-testers
Freya inherits core components from Ubuntu 14.04.1 LTS such as the Linux kernel (version 3.13), hardware drivers, and graphics stack. This includes support for EFI stub-loading, which is a kernel feature that enables booting directly from (U)EFI, without the need for an additional bootloader such as GRUB. Ubiquity does not yet have support for this configuration, but one of our developers has created a guide for a GRUB-free install of Freya on modern Mac computers using rEFInd.
Additionally, we’re shipping the latest stable GTK+ release, 3.12, rather than Ubuntu 14.04’s outdated 3.10. This beta release brings a number of new features including new widgets and an improved GtkCSSProvider. Vala has been updated to version 0.24 bringing an incredible number of new bindings to elementary OS including Gstreamer 1.0, GeoCode, and more.
Could you please provide support for the various spins of linuxbbq (which in fact are all different debian distros)?
http://linuxbbq.org
Many thanks!
I am part of BOSS Gnu/Linux distribution (http://bosslinux.in/) which is an derivative of debian, When i tried to install i was threw an error "## Your distribution, identified as "anokha", is not currently supported", We will be glad if this is solved, And if their is anything that we have to do from our end
we are ready to do that.
Tried to use this on Linux Mint Debian Edition, version jessie. It read the distro as "debian" because this is what was returned by lsb_release -c -s
. As a result it could not find the package.
Hacking it to use the string 'jessie' was a successful workaround.
Maybe it should look in /etc/debian_version for the distro (taking the bit before the slash) in this case?
How would you recommend that someone use this repository to install a specific version of Node.js? Previously, I was attempting to pin the version number, but it looks like older versions of Node.js are being replaced with newer ones.
My goal is to use a specific version of Node.js, but then not update to the newest version until after some testing occurs.
When I use the original HTTPS URLs in my deb
and deb-src
lines, aptitude tries to build a CONNECT tunnel through my apt-cacher-ng, which of course is denied because its purpose is to cache the downloaded packages, not just let them pass.
When I remove the s
from https://
, apt-cacher-ng fails to download the packages, unfortunately without any hint in its error log.
Is there a way to still get the packages through apt-cacher-ng?
Are there plain HTTP mirrors?
They should still be safe sources verified by the GnuPG signatures, right?
Overview as of 2016-05-29:
workarounds: abstain from caching or setup a mirror
solutions: for apt-cacher-ng
apt repo attack vectors: replay stale metadata, identify missing security updates
Hi,
I got 403 forbidden when trying to access this file:
https://rpm.nodesource.com/pub/el/6/SRPMS/repodata/db0852512678d58b7a87bf48658c6162e8210694-filelists.sqlite.bz2
Is the server miss configured?
cheers,
Justin
Hello,
I got today the following error message:
"## Your distribution, identified as "squeeze", 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".
Can you fix that or tell me how I can fix that?
Thanks in advance,
Thomas
Tried to use Distributions on a Petra edition of Linux Mint and it didn't worked.
Hello. Is this expected? Is there a way to revert to 0.10.x?
Package: nodejs
Version: 0.11.15-1nodesource1~utopic1
Architecture: amd64
Maintainer: Jérémy Lal <[email protected]>
Installed-Size: 24599
Depends: libc6 (>= 2.15), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.9), rlwrap
Conflicts: nodejs-dev, nodejs-legacy, npm
Replaces: nodejs-dev (<= 0.8.22), nodejs-legacy, npm (<= 1.2.14)
Provides: nodejs-dev, nodejs-legacy, npm
Homepage: http://nodejs.org/
Priority: extra
Section: web
Filename: pool/main/n/nodejs/nodejs_0.11.15-1nodesource1~utopic1_amd64.deb
Size: 5698932
SHA256: 99731ceeaebcf1aba9e5d4148b803392db24e05c85551e8aad5549db4b831986
SHA1: 889acee2a935a56fdeb5b001eeeba4235fca4c7c
MD5sum: 40244d6d0629bd11b9bc1a22d22f51e2
It seems that your package doesn't add /usr/local/... to NODE_PATH but npm install package there.
It could be a problem of debian official packages as well. I'll check shortly.
thanks
I installed node with apt-get install nodejs and it worked, except it was outdated and the npm was also outdated. I installed the newest version and after installment after I type 'node' or executing a basic script it just hangs and nothing happens except when I check the version (v0.10.34) (npm also hangs). Sorry if this is a bad issue it's my first time doing it.
@chrislea this is for you but I'm more than happy to do some of the work if you can provide pointers.
The main trick for io.js support is the minimum requirement of gcc 4.8, which is a pain on everything but the latest distros. These are yaks I've already shaved for the CI machines here and the CI containers here but I'm not sure how transferrable that info is to the pbuilder process.
curl -sL http://linuxsoft.cern.ch/cern/devtoolset/slc6-devtoolset.repo -o /etc/yum.repos.d/slc6-devtoolset.repo
rpm --import http://ftp.scientificlinux.org/linux/scientific/5x/x86_64/RPM-GPG-KEYs/RPM-GPG-KEY-cern
curl http://linuxsoft.cern.ch/cern/scl/slc6-scl.repo -o /etc/yum.repos.d/slc6-scl.repo
# then run the build within a devtoolset-2 bash or directly with:
scl enable devtoolset-2 [bash or make or whatever command needs newer gcc]
cul -sL http://dl.fedoraproject.org/pub/epel/5/{{ server_arch }}/epel-release-5-4.noarch.rpm -o /tmp/epel-release-5-4.noarch.rpm
bash -c 'rpm -Uvh /tmp/epel-release-5-4.noarch.rpm || true'
yum install python-hashlib # needed for the newer format of slc5-rpm
curl -sL http://linuxsoft.cern.ch/cern/devtoolset/slc5-devtoolset.repo -o /etc/yum.repos.d/slc5-rpm --import http://ftp.scientificlinux.org/linux/scientific/5x/{{ server_arch }}/RPM-GPG-KEYs/RPM-GPG-KEY-cern
# then run the build within a devtoolset-2 bash or directly with:
scl enable devtoolset-2 [bash or make or whatever command needs newer gcc]
echo 'deb https://deb.nodesource.com/weezy-gcc49 weezy-gcc49 main' >> /etc/apt/sources.list && \
curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
apt-get install g++-4.9 gcc-4.9 cpp-4.9
# set alternatives for cc, gcc and g++ to 4.9
Hi,
I'm trying to use your service to install the latest nodejs, v0.12 -- but I can't find instructions for it (https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories)
Could you give a hand?
Node.js is not automatically being upgraded on my Ubuntu 14.04 machine. The config for unattended-upgrades looks like this:
Unattended-Upgrade::Allowed-Origins {
[...]
"Node Source:trusty";
};
I noticed that https://deb.nodesource.com/node/dists/trusty/main/binary-amd64/Release doesn't contain an Archive
property, like http://ppa.launchpad.net/chris-lea/node.js/ubuntu/dists/trusty/main/binary-amd64/Release does. (The config file asks for an origin:archive
pair.) Could this be the problem?
We won't be officially supporting Utopic until it's released by Canonical, towards the end of October. In the meantime, the Trusty binaries should work fine, simply run this as root to try it out:
apt-get update && apt-get install curl apt-transport-https -y
curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
echo 'deb https://deb.nodesource.com/node trusty main' > /etc/apt/sources.list.d/nodesource.list
echo 'deb-src https://deb.nodesource.com/node trusty main' >> /etc/apt/sources.list.d/nodesource.list
apt-get update && apt-get install nodejs -y
node -v && npm -v
Additionally, to support building native add-ons:
apt-get install build-essential python -y
To confirm a full, working installation:
curl -sL https://deb.nodesource.com/test | bash -
What is the problem here?
I already have nodejs
installed via Ubuntu repos
$ curl -sL https://deb.nodesource.com/setup | sudo bash -
[sudo] password for myUser:
## Populating apt-get cache...
# my repos list
## 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
curl -sL https://rpm.nodesource.com/setup | bash -
Inspecting system...
Could not determine your distribution version, you may not be running a supported version of Enterprise Linux. Please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect. Include your 'distribution package'
Please let me know if you need any more info. Thank you!
Before, when the nodejs binaries were located here:
https://launchpad.net/~chris-lea/+archive/ubuntu/node.js-devel
It was possible to check (visually) which versions are available.
Could someone tell me how we can do the same for the nodesource repository ?
Because I still don't know if the 0.12 version is already there :)
Regards,
On Debian Systems, al least with 7.0 ( Wheezy ) apt-transport-https is not installed by default, altough it is required for using the https nodesource repos.
Can we may add it to the list of needed packages besides curl and lsb-release ?
Hi,
I stumbled into what seems to be an issue with wheezy:
cat /etc/apt/sources.list.d/nodesource.list
deb https://deb.nodesource.com/node wheezy main
deb-src https://deb.nodesource.com/node wheezy main
curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
and when I apt-get update, I get:
Ign https://deb.nodesource.com wheezy Release.gpg
Ign https://deb.nodesource.com wheezy Release
Err https://deb.nodesource.com wheezy/main Sources
Problem with the SSL CA cert (path? access rights?)
Err https://deb.nodesource.com wheezy/main amd64 Packages
Problem with the SSL CA cert (path? access rights?)
Atteint http://security.debian.org wheezy/updates Release.gpg
Atteint http://security.debian.org wheezy/updates Release
Réception de : 3 http://security.debian.org wheezy/updates/main amd64 Packages [276 kB]
3 o réceptionnés en 5s (0 o/s)
W: Impossible de récupérer https://deb.nodesource.com/node/dists/wheezy/main/source/Sources Problem with the SSL CA cert (path? access rights?)
W: Impossible de récupérer https://deb.nodesource.com/node/dists/wheezy/main/binary-amd64/Packages Problem with the SSL CA cert (path? access rights?)
Hi there I using a Beaglebone Black with Debian wheezy.
PRETTY_NAME="Debian GNU/Linux 7 (wheezy)"
NAME="Debian GNU/Linux"
VERSION_ID="7"
VERSION="7 (wheezy)"
ID=debian
And this is the error:
Confirming "wheezy" is supported...
curl -sLf -o /dev/null 'https://deb.nodesource.com/node/dists/wheezy/Release'
Your distribution, identified as "wheezy", 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
But in https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager says this:
Supported Debian versions:
Debian 7 / stable (wheezy)
A lot of devs ( myself included ) have begun moving to ubuntu+1 ( 15.04 codenamed "vivid" ) - could you add support for that release to your deb scripts?
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.
I used the install script hosted at https://rpm.nodesource.com/setup - it seems fedora 21 isn't currently supported. There was an issue raised about this when fedora 21 was still Alpha #31 but it is now closed.
We are a little over month away from the official release and git repo already has Vivid support. Would be nice if you could add support for Vivid release too.
Preparing to unpack .../nodejs_0.10.31-1chl1~trusty1_amd64.deb ...
Unpacking nodejs (0.10.31-1chl1~trusty1) over (0.10.25~dfsg2-2ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/nodejs_0.10.31-1chl1~trusty1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/node.1.gz', which is also in package nodejs-legacy 0.10.25~dfsg2-2ubuntu1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.6.7.1-1) ...
Errors were encountered while processing:
/var/cache/apt/archives/nodejs_0.10.31-1chl1~trusty1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
nodejs-legacy
provides a symlink from /usr/bin/node
to /usr/bin/nodejs
which is very helpful if you are used to Node.js being installed as node
.
I think that the correct solution is to mark this package as conflicting with nodejs-legacy
and, if nodesource is providing the symlink, mark it as replacing.
## Your distribution, identified as "rebecca", 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
Mint 'rebecca' is basically Ubuntu 'trusty', aside from using cinnamon for the GUI. Should be easy to support.
It can be obtained from source RPM, but it would be nice to have it on github.
The nodejs
packages in Debian are split into nodejs
and nodejs-legacy
to avoid conflicting with a pre-existing node
tool.
I think it's fine not to do that in your packages, but could you add a Conflicts: nodejs-legacy
line so that the upstream package gets automatically uninstalled on installing yours?
If you don't manually remove the nodejs-legacy
package right now you get an extremely unhelpful error message like:
dpkg: error processing /vagrant/repository/pool/main/n/nodejs/nodejs_0.10.33-1nodesource1~wheezy1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/node.1.gz', which is also in package nodejs-legacy 0.10.2~dfsg1-1
I'm getting an error saying debian squeeze is not supported when using:
curl -sL https://deb.nodesource.com/setup | bash -
Output:
:~# curl -sL https://deb.nodesource.com/setup | bash -
## Populating apt-get cache...
+ apt-get update
Hit http://nginx.org squeeze Release.gpg
Ign http://nginx.org/packages/debian/ squeeze/nginx Translation-en
Hit http://nginx.org squeeze Release
Hit http://ftp.debian.org squeeze Release.gpg
Ign http://ftp.debian.org/debian/ squeeze/contrib Translation-en
Ign http://ftp.debian.org/debian/ squeeze/main Translation-en
Ign http://ftp.debian.org/debian/ squeeze/non-free Translation-en
Hit http://security.debian.org squeeze/updates Release.gpg
Ign http://security.debian.org/ squeeze/updates/contrib Translation-en
Ign http://security.debian.org/ squeeze/updates/main Translation-en
Ign http://security.debian.org/ squeeze/updates/non-free Translation-en
Ign http://nginx.org squeeze/nginx Sources
Ign http://nginx.org squeeze/nginx amd64 Packages
Hit http://ftp.debian.org squeeze Release
Hit http://security.debian.org squeeze/updates Release
Hit http://nginx.org squeeze/nginx Sources
Ign http://ftp.debian.org squeeze/main amd64 Packages
Hit http://nginx.org squeeze/nginx amd64 Packages
Ign http://security.debian.org squeeze/updates/main amd64 Packages
Ign http://ftp.debian.org squeeze/contrib amd64 Packages
Ign http://ftp.debian.org squeeze/non-free amd64 Packages
Ign http://security.debian.org squeeze/updates/contrib amd64 Packages
Ign http://security.debian.org squeeze/updates/non-free amd64 Packages
Hit http://ftp.debian.org squeeze/main amd64 Packages
Hit http://ftp.debian.org squeeze/contrib amd64 Packages
Hit http://security.debian.org squeeze/updates/main amd64 Packages
Hit http://ftp.debian.org squeeze/non-free amd64 Packages
Hit http://security.debian.org squeeze/updates/contrib amd64 Packages
Hit http://security.debian.org squeeze/updates/non-free amd64 Packages
Reading package lists... Done
## Confirming "squeeze" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node/dists/squeeze/Rel
## Your distribution, identified as "squeeze", is not currently supported, e contact NodeSource at https://github.com/nodesource/distributions/issues u think this is incorrect or would like your distribution to be considered upport
I followed the Debian and Ubuntu based Linux distributions instructions.
When I run node
or npm
a segmentation fault occurs.
pi@raspberrypi ~ $ node -v
Segmentation fault
pi@raspberrypi ~ $ npm -v
Segmentation fault
GDB output:
pi@raspberrypi ~ $ gdb /usr/bin/node
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/node...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/node
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x001e8fd2 in DES_xcbc_encrypt ()
(gdb) bt
#0 0x001e8fd2 in DES_xcbc_encrypt ()
(gdb)
Install output:
pi@raspberrypi ~ $ sudo apt-get install nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
rlwrap
The following NEW packages will be installed:
nodejs rlwrap
0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/5,671 kB of archives.
After this operation, 17.6 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Selecting previously unselected package rlwrap.
(Reading database ... 78080 files and directories currently installed.)
Unpacking rlwrap (from .../rlwrap_0.37-3_armhf.deb) ...
Selecting previously unselected package nodejs.
Unpacking nodejs (from .../nodejs_0.10.33-2nodesource1~wheezy1_armhf.deb) ...
Processing triggers for man-db ...
Setting up rlwrap (0.37-3) ...
update-alternatives: using /usr/bin/rlwrap to provide /usr/bin/readline-editor (readline-editor) in auto mode
Setting up nodejs (0.10.33-2nodesource1~wheezy1) ...
Ran a sudo apt-get update && sudo apt-get upgrade
before node setup/install.
Supporting a keyserver such as keys.gnupg.net or keyserver.ubuntu.com would allows us to easier implement the repository with configuration management systems such as salt, puppet, chef or ansible.
All that is required is to submit the key to the key server and publish the key id.
http://debian.tagancha.org/debian/dists/stable/main/binary-i386/Packages 404 Not Found
When I run scripts in a unicode language environment, the script give me a segment fault error.
curl -sL https://deb.nodesource.com/setup | sudo bash -
## Populating apt-get cache...
+ apt-get update
命中 http://dl.google.com stable Release.gpg
命中 http://dl.google.com stable Release.gpg
...
bash: 行 28: 1877 段错误 (核心已转储) bash -c "$1"
Error executing command, exiting
It said in line 28 a segment fault occured.
locale:
LANG=zh_CN.UTF-8
LANGUAGE=zh_CN:en
LC_CTYPE="zh_CN.UTF-8"
LC_NUMERIC=zh_CN.UTF-8
LC_TIME=zh_CN.UTF-8
LC_COLLATE="zh_CN.UTF-8"
LC_MONETARY=zh_CN.UTF-8
LC_MESSAGES="zh_CN.UTF-8"
LC_PAPER=zh_CN.UTF-8
LC_NAME=zh_CN.UTF-8
LC_ADDRESS=zh_CN.UTF-8
LC_TELEPHONE=zh_CN.UTF-8
LC_MEASUREMENT=zh_CN.UTF-8
LC_IDENTIFICATION=zh_CN.UTF-8
LC_ALL=
bash --version
GNU bash, version 4.2.25(1)-release (i686-pc-linux-gnu)
While setting locale to LANG=C
, everything work fine.
~$ LANG=C curl -sL https://deb.nodesource.com/setup | sudo bash -
I am wondering if it occured in other unicode character language. Although it could run by setting LANG=C
, it's more convience for others if you cloud solve this.
Not working in Kali. I've taken a quick look and there's a problem installing the pkg "apt-transport-https" and another one (at least) because the "lsb_release" of the distro is not working correctly. Could you take a look please? :)
There's currently no license specified, so most likely, it defaults to copyrighted with "All Rights Reserved", which means users cannot fork, modify, or distribute the repo.
user@user-HP-ProBook-4530s:~/atom$ curl -sL https://deb.nodesource.com/setup | sudo -E bash -
[sudo] password for user:
## Populating apt-get cache...
+ apt-get update
Ign http://ppa.launchpad.net trusty InRelease
Hit http://es.archive.trisquel.info belenos InRelease
Hit http://ppa.launchpad.net trusty Release.gpg
Hit http://es.archive.trisquel.info belenos-security InRelease
Hit http://ppa.launchpad.net trusty Release
Hit http://es.archive.trisquel.info belenos-updates InRelease
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Hit http://es.archive.trisquel.info belenos/main Sources
Hit http://ppa.launchpad.net trusty/main i386 Packages
Hit http://es.archive.trisquel.info belenos/main amd64 Packages
Hit http://ppa.launchpad.net trusty/main Translation-en
Hit http://es.archive.trisquel.info belenos/main i386 Packages
Hit http://es.archive.trisquel.info belenos/main Translation-en
Hit http://es.archive.trisquel.info belenos-security/main Sources
Hit http://es.archive.trisquel.info belenos-security/main amd64 Packages
Hit http://es.archive.trisquel.info belenos-security/main i386 Packages
Hit http://es.archive.trisquel.info belenos-updates/main Sources
Hit http://es.archive.trisquel.info belenos-updates/main amd64 Packages
Hit http://es.archive.trisquel.info belenos-updates/main i386 Packages
Ign http://es.archive.trisquel.info belenos/main Translation-en_US
Ign http://es.archive.trisquel.info belenos-security/main Translation-en_US
Ign http://es.archive.trisquel.info belenos-security/main Translation-en
Ign http://es.archive.trisquel.info belenos-updates/main Translation-en_US
Ign http://es.archive.trisquel.info belenos-updates/main Translation-en
Reading package lists... Done
## Confirming "belenos" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node/dists/belenos/Release'
## Your distribution, identified as "belenos", 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
Hi, performing the curl command, the script exits after the following error line:
Failed to fetch https://deb.nodesource.com/node/dists/wheezy/Release Unable to find expected entry 'main/binary-armel/Packages' in Release file (Wrong sources.list entry or malformed file)
As far as i can see, the full node subdir node is no longer existing.
Implemented the suggested tests from pull request #12 in the branch hardcore.
It failed 5 of the npm unit tests and had a hickup in the yeoman script.
Command that triggered the tests (where $PWD
is the root of the distributions repo):
docker run -dv ${PWD}:/test hardcore /test/hardcore
Here is the Dockerfile used to generate the hardcore container.
Here is the new test script.
Here is the result of running the new test script in the hardcore container.
(also note the script is generating markdown 😄)
I'm on Lubuntu 14.04 64-bit.
$ node -v
$ npm -v
1.4.28
I ran the tests and it says it installed correctly.
npm
seems to work fine, but node
does not.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.