-
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
Fail to install nodejs 6.x/8.x for debian jessie #532
Comments
Got the same thing with wheezy. |
This issue is affecting me as well for Debian Jessie. Installing the NodeSource Node.js v8.x repo...Populating apt-get cache...
Confirming "n/a" is supported...
Your distribution, identified as "n/a", 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 supportroot@debian-jessie:~# |
Same issues with 7.x or 6.x release |
Apparently I have found a solution for this. For your particular version of Debian/Ubuntu add the respective line to your sources.list file Let me know, if this was helpful to you. Thanks |
Buenas tardes a mi me presenta el mismo error que a ustedes y no me soluciona lo que recomendaste rajudev |
@ARET-METAL Apologies,I don't understand your language. Would be great if you can repeat the message in English. |
I'm having problems installing taiga in debian jessie in dependencies and nodejs they will have an installation manual, thanks |
npm -v |
@ARET-METAL Have you resolved your issue within the last three days? If it is still there I can still help. |
@ARET-METAL Since you are already having npm installed, although an older version. |
@rajudev While tried to added responsitory key the errors showed: "gpg: no valid OpenPGP data found." |
@Marksion08 You need add the the keys for the repository. |
Hi, |
Expanding on @JoSchmutz solution is to make sure that the RPis datetime is updated automatically: |
Same issue here, I installed nodejs v0.10.29 through |
I think the problem is you're passing the
and let us know what happens? |
@chrislea it doesn't work :( |
@kenshinji okay can you please run
and past the full output here? Thanks. |
You should run |
I've just (re)done the installation on Debian jessie and it does not work !! bad version of node and unable to run npm !! `***# date /usr/lib/node_modules/npm/lib/utils/unsupported.js:27 node.js:201 |
@jo-argo7 did you do |
@jo-argon7 make sure you are on jessie image and not stretch |
yep, result is in /etc/apt/sources.list.d/nodesource.list |
Debian Jessie confirmed: |
What do you get with that: curl -sL https://deb.nodesource.com/setup_7.x | sudo -E bash - |
I've found another method and it works: and now everything's ok: |
Again, please run exactly:
and paste the full output here. This may help me see what's going on with the installer script. |
output saved in file: |
i'm on debian 9 and had the same "n/a" error :
even tho $cat /etc/debian_version
and
so i followed @rajudev advice and added
and
Did
and finished with
So now:
|
This is because the script use lsb_release to determine the codename. DISTRO=$(lsb_release -c -s) However, on my Raspbian, lsb_release -c show: I fixed it by download the setup_9.x and manually change the line to: DISTRO=jessie |
Im on debian 8, in Deepin 15.07 64bits and have the same error, when write "npm -v", show thw following issue: bash: npm didn't found the order |
This worked for me. |
This has ben fixed a while ago. |
I tried to install nodejs 6.x/8.x for debian 8, after followed many way to, but this problem still.
It showed me as below:
Confirming "jessie" is supported...
Your distribution, identified as "jessie", 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
BTW: debian 8 jessie was download from the official-side.
PLS tell me if there was any wrong, I was fresh in Debian.
Thanks & Regards,
Marksion
The text was updated successfully, but these errors were encountered: