I had the same issue. The problem is not the nodejs installation script but another package in your package list in /etc/apt/sources.list.
The following worked for me:
1) Create backup of the file /etc/apt/sources.list just to be on the safe side:
sudo cp /etc/apt/sources.list /etc/apt/sources.list.bu
2) Remove the packages that cause the issue:
Open /etc/apt/sources.list with root permissions, e.g.
sudo nano /etc/apt/sources.list
and remove the
http://ppa.launchpad.net/tualatrix/next/ubuntu/dists/xenial/main/binary-amd64/Packages
parts. In my case it was skype that caused the issue; you can identify the critical packages by the lines that start with E: Failed to fetch.
Afterwards, the following works fine (taken from the installation instructions):
cd ~
curl -sL https://deb.nodesource.com/setup_8.x -o nodesource_setup.sh
sudo bash nodesource_setup.sh
sudo apt-get install nodejs
sudo apt-get install build-essential
If one then types
nodejs -v
it will return
v8.9.4
(or whatever version you specified).
In case you already have anaconda installed, I recommend to install node.js inside an environment which keeps things clean. A detailed explanation on how to do this can be found here. Basically all it needs is
conda create -n webdev nodejs
plus desired python modules in case you would like to use e.g. Flask or Django.
Содержание
- Error executing command, exiting — Ошибка при обновлении/установки. E: Failed to fetch как исправить
- Primary tabs
- Forums:
- Проблема
- Решение
- Key Words for FKN + antitotal forum (CS VSU):
- The following signatures were invalid
- Error executing command, exiting — KDE Neon 5.19 (Ubuntu 20.04) #1108
- Comments
- Unable to install Node 14.x in Ubuntu 18.04 #1227
- Comments
- Installing the NodeSource Node.js 14.x repo.
- Populating apt-get cache.
- Footer
- Could not resolve ‘in.old-releases.ubuntu.com’ || Error executing command, exiting || See apt-secure(8) manpage for repository creation and user configuration details. #1333
- Comments
- Installing the NodeSource Node.js 17.x repo.
- Populating apt-get cache.
- Unable to install Node 14.x in Ubuntu 18.04 #1227
- Comments
- Installing the NodeSource Node.js 14.x repo.
- Populating apt-get cache.
- Footer
Error executing command, exiting — Ошибка при обновлении/установки. E: Failed to fetch как исправить
Primary tabs
Forums:
Проблема
Если вы получаете список предупреждений вида:
W: The repository ‘http://download.virtualbox.org/virtualbo. xenial InRelease’ is not signed.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 Release: The following signatures were invalid: KEYEXPIRED 1507497109
W: The repository ‘http://ppa.launchpad.net/rabbitvcs/ppa/u. xenial Release’ does not have a Release file.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Failed to fetch http://repo.mongodb.org/apt/ubuntu/dists. The following signatures were invalid: KEYEXPIRED 1507497109
E: Failed to fetch http://ppa.launchpad.net/rabbitvcs/ppa/u. 404 Not Found
W: Some index files failed to download. They have been ignored, or old ones used instead.
W: Target Packages (partner/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:43 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Packages (partner/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:43 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Packages (partner/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:43 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Translations (partner/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:43 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target Translations (partner/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:43 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target DEP-11 (partner/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list:43 and /etc/apt/sources.list.d/xenial-partner.list:4
W: Target DEP-11-icons (partner/dep11/icons-64×64.tar) is configured multiple times in /etc/apt/sources.list:43 and /etc/apt/sources.list.d/xenial-partner.list:4
Error executing command, exiting
Решение
— то необходимо исправить хотя самые критические, а именно ошибки («E:»)? в моём случае, это E: Failed to fetch. а именно:
Поэтому я поправил файл просто закоментировав в нем репозиторий:
Key Words for FKN + antitotal forum (CS VSU):
Tue, 09/17/2019 — 10:42
The following signatures were invalid
Err:9 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 Release.gpg
The following signatures were invalid: KEYEXPIRED 1507497109
В данном случае к ошибке приводит то, что ключ устарел, закомментирован репозиторий монги в:
_____________
матфак вгу и остальная классика =)
Источник
Error executing command, exiting — KDE Neon 5.19 (Ubuntu 20.04) #1108
When trying to install nodejs via the repository, using release 12,x or 14.x gives error, although «focal» is supported.
curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash — sudo apt-get install -y nodejs
$ curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash —
## Installing the NodeSource Node.js 12.x repo.
## Populating apt-get cache.
+ apt-get update Obj:1 http://ppa.launchpad.net/papirus/papirus/ubuntu focal InRelease Obj:2 http://download.opensuse.org/repositories/home:/ColinDuquesnoy/xUbuntu_20.04 InRelease Obj:3 http://security.ubuntu.com/ubuntu focal-security InRelease Obj:4 http://dl.google.com/linux/chrome/deb stable InRelease Obj:5 http://ppa.launchpad.net/teejee2008/timeshift/ubuntu focal InRelease Des:6 http://archive.neon.kde.org/user focal InRelease [155 kB] Des:7 https://mega.nz/linux/MEGAsync/xUbuntu_20.04 ./ InRelease [2.441 B] Obj:8 http://packages.microsoft.com/repos/vscode stable InRelease Obj:9 http://es.archive.ubuntu.com/ubuntu focal InRelease Obj:10 http://es.archive.ubuntu.com/ubuntu focal-updates InRelease Obj:11 http://es.archive.ubuntu.com/ubuntu focal-backports InRelease Descargados 158 kB en 2s (91,5 kB/s) Leyendo lista de paquetes. Hecho
## Confirming «focal» is supported.
+ curl -sLf -o /dev/null ‘https://deb.nodesource.com/node_12.x/dists/focal/Release’
## Adding the NodeSource signing key to your keyring.
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add — gpg: invalid key resource URL ‘/etc/apt/trusted.gpg.d/home:ColinDuquesnoy.gpg’ gpg: recurso de bloque de claves ‘(null)’: Error general gpg: key 7721F63BD38B4796: 2 firmas no comprobadas por falta de claves gpg: key E481C081DB2A84F7: 1 firma no comprobada por falta de una clave gpg: key E6D4736255751E5D: 1 firma no comprobada por falta de una clave gpg: key 3B4FE6ACC0B21F32: 3 firmas no comprobadas por falta de claves gpg: key D94AA3F0EFE21092: 3 firmas no comprobadas por falta de claves gpg: key 871920D1991BC93C: 1 firma no comprobada por falta de una clave gpg: Cantidad total procesada: 13 gpg: omitidas nuevas claves: 13 Error executing command, exiting
It’s in spanish, but basically means that it couldn’t check the signature, because keys are missing.
Any help would be appreciated, thanks.
The text was updated successfully, but these errors were encountered:
Источник
Unable to install Node 14.x in Ubuntu 18.04 #1227
curl -fsSL https://deb.nodesource.com/setup_14.x | sudo -E bash —
sudo apt-get install -y nodejs
Installing the NodeSource Node.js 14.x repo.
Populating apt-get cache.
- apt-get update
Hit:1 http://azure.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://azure.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://azure.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:4 https://deb.nodesource.com/node_14.x bionic InRelease [4584 B]
Hit:5 https://download.docker.com/linux/ubuntu bionic InRelease
Get:6 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [2099 kB]
Get:7 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:8 http://azure.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1736 kB]
Err:4 https://deb.nodesource.com/node_14.x bionic InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
Reading package lists. Done
W: GPG error: https://deb.nodesource.com/node_14.x bionic InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
E: The repository ‘https://deb.nodesource.com/node_14.x bionic InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Error executing command, exiting
The text was updated successfully, but these errors were encountered:
Similar output here, on Ubuntu 18.04.5 (as provided from Azure’s VM image). Ran this as root:
I had the same issue today.
The permissions for the key were not set correctly by the script. I don’t know why, but I think GPG complained about too strict permissions.
A sudo chmod +644 /usr/share/keyrings/nodesource.gpg did the trick and the apt-update went through.
Maybe this could be added to the installation script?
Hope this helps,
Matthias
I had to run the below commands to remove the PPAs and download Node and NPM from https://nodejs.org/dist/v14.17.1/node-v14.17.1-linux-x64.tar.xz and manually place them in /usr/bin
sudo rm -rf /var/lib/apt/lists/*
sudo rm -rf /etc/apt/sources.list.d/*
sudo apt-get update
Do NOT run these instructions, reader on the internet. This will remove ALL of your PPAs. Please at least limit your command to node PPAs if you’re going to post something so destructive.
Luckily I caught it in time and didn’t run it myself.
m-terlinde’s commant above worked for me. The file was 400 and changing to 644 worked.
Happy to hear, @sglajchEG!
Maybe I should do a FAQ entry for this issue.
Or the maintainer could add this little chmod to the installation script.
I had the same issue today. The permissions for the key were not set correctly by the script. I don’t know why, but I think GPG complained about too strict permissions.
A sudo chmod +644 /usr/share/keyrings/nodesource.gpg did the trick and the apt-update went through. Maybe this could be added to the installation script?
Hope this helps, Matthias
this works well
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
Could not resolve ‘in.old-releases.ubuntu.com’ || Error executing command, exiting || See apt-secure(8) manpage for repository creation and user configuration details. #1333
Installing the NodeSource Node.js 17.x repo.
Populating apt-get cache.
- apt-get update
Err:1 http://in.old-releases.ubuntu.com/ubuntu eoan InRelease
Could not resolve ‘in.old-releases.ubuntu.com’
Err:2 http://in.old-releases.ubuntu.com/ubuntu eoan-updates InRelease
Could not resolve ‘in.old-releases.ubuntu.com’
Err:3 http://in.old-releases.ubuntu.com/ubuntu eoan-backports InRelease
Could not resolve ‘in.old-releases.ubuntu.com’
Ign:4 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu eoan InRelease
Ign:5 http://old-releases.ubuntu.com/ubuntu bionic InRelease
Ign:6 http://ppa.launchpad.net/linuxjedi/ppa/ubuntu eoan InRelease
Ign:7 http://old-releases.ubuntu.com/ubuntu bionic-security InRelease
Err:8 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu eoan Release
404 Not Found [IP: 91.189.95.85 80]
Ign:9 http://old-releases.ubuntu.com/ubuntu bionic-updates InRelease
Hit:10 http://deb.playonlinux.com trusty InRelease
Hit:11 http://old-releases.ubuntu.com/ubuntu eoan InRelease
Err:12 http://ppa.launchpad.net/linuxjedi/ppa/ubuntu eoan Release
404 Not Found [IP: 91.189.95.85 80]
Ign:13 http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 InRelease
Hit:14 http://old-releases.ubuntu.com/ubuntu eoan-security InRelease
Err:15 http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 Release
404 Not Found [IP: 195.135.221.134 80]
Err:16 http://old-releases.ubuntu.com/ubuntu bionic Release
404 Not Found [IP: 91.189.91.124 80]
Err:17 http://old-releases.ubuntu.com/ubuntu bionic-security Release
404 Not Found [IP: 91.189.91.124 80]
Err:18 http://old-releases.ubuntu.com/ubuntu bionic-updates Release
404 Not Found [IP: 91.189.91.124 80]
Reading package lists. Done
E: The repository ‘http://ppa.launchpad.net/deadsnakes/ppa/ubuntu eoan Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘http://ppa.launchpad.net/linuxjedi/ppa/ubuntu eoan Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘http://old-releases.ubuntu.com/ubuntu bionic Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘http://old-releases.ubuntu.com/ubuntu bionic-security Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘http://old-releases.ubuntu.com/ubuntu bionic-updates Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Error executing command, exiting
The text was updated successfully, but these errors were encountered:
http://in.old-releases.ubuntu.com/ubuntu is invalid; and is not a bug, but a user error (ie. the person who added it to your system was in error & should have checked the URL)
http://ppa.launchpad.net/deadsnakes/ppa/ubuntu does not provide support for eoan or 19.10; so again a user error (the person who added it didn’t do their checks & thus should never have added it)
http://old-releases.ubuntu.com/ubuntu bionic likewise is invalid; it’s a supported release thus isn’t found in old-releases..
I didn’t read further, this is just three user-errors.
Your issue is the operator who was given sudo rights isn’t doing their homework before adding/changing sources, and should be seeking support; not raising bug tickets (unless it’s with their teachers of IT/technology who didn’t instruct well enough)
Thanks ❤ , the issue is resolved now
i change whole OS by iso into 20.04 😅
maybe the links I am updating in sources.lists are not the latest one because I was trying stackoverflow questions Links not from the official ubuntu archives links
@guiverc thank you for helping us to solve this issue.
Источник
Unable to install Node 14.x in Ubuntu 18.04 #1227
curl -fsSL https://deb.nodesource.com/setup_14.x | sudo -E bash —
sudo apt-get install -y nodejs
Installing the NodeSource Node.js 14.x repo.
Populating apt-get cache.
- apt-get update
Hit:1 http://azure.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://azure.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://azure.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:4 https://deb.nodesource.com/node_14.x bionic InRelease [4584 B]
Hit:5 https://download.docker.com/linux/ubuntu bionic InRelease
Get:6 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [2099 kB]
Get:7 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:8 http://azure.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1736 kB]
Err:4 https://deb.nodesource.com/node_14.x bionic InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
Reading package lists. Done
W: GPG error: https://deb.nodesource.com/node_14.x bionic InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
E: The repository ‘https://deb.nodesource.com/node_14.x bionic InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Error executing command, exiting
The text was updated successfully, but these errors were encountered:
Similar output here, on Ubuntu 18.04.5 (as provided from Azure’s VM image). Ran this as root:
I had the same issue today.
The permissions for the key were not set correctly by the script. I don’t know why, but I think GPG complained about too strict permissions.
A sudo chmod +644 /usr/share/keyrings/nodesource.gpg did the trick and the apt-update went through.
Maybe this could be added to the installation script?
Hope this helps,
Matthias
I had to run the below commands to remove the PPAs and download Node and NPM from https://nodejs.org/dist/v14.17.1/node-v14.17.1-linux-x64.tar.xz and manually place them in /usr/bin
sudo rm -rf /var/lib/apt/lists/*
sudo rm -rf /etc/apt/sources.list.d/*
sudo apt-get update
Do NOT run these instructions, reader on the internet. This will remove ALL of your PPAs. Please at least limit your command to node PPAs if you’re going to post something so destructive.
Luckily I caught it in time and didn’t run it myself.
m-terlinde’s commant above worked for me. The file was 400 and changing to 644 worked.
Happy to hear, @sglajchEG!
Maybe I should do a FAQ entry for this issue.
Or the maintainer could add this little chmod to the installation script.
I had the same issue today. The permissions for the key were not set correctly by the script. I don’t know why, but I think GPG complained about too strict permissions.
A sudo chmod +644 /usr/share/keyrings/nodesource.gpg did the trick and the apt-update went through. Maybe this could be added to the installation script?
Hope this helps, Matthias
this works well
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
I’m trying to install node.js 12 on Ubuntu 18 and following the instructions, when I type
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
I got the next text:
Reading package lists... Done
E: The repository 'http://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.4 Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.0 Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_18.10 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4ABE1AC7557BEFF9
E: The repository 'http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_18.10 Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.6 Release: The following signatures were invalid: EXPKEYSIG 58712A2291FA4AD5 MongoDB 3.6 Release Signing Key <packaging@mongodb.com>
E: The repository 'http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.6 Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Error executing command, exiting
I guess this is the reason why every time that I run
sudo apt-get install -y nodejs
I got the version 8 instead of 10.
Anyone knows why is this happening? How I got to this point?
And if the security of my system is at risk, how to fix it?
When trying to install nodejs via the repository, using release 12,x or 14.x gives error, although «focal» is supported.
curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash - sudo apt-get install -y nodejs
Gives
$ curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
## Installing the NodeSource Node.js 12.x repo...
## Populating apt-get cache...
+ apt-get update Obj:1 http://ppa.launchpad.net/papirus/papirus/ubuntu focal InRelease Obj:2 http://download.opensuse.org/repositories/home:/ColinDuquesnoy/xUbuntu_20.04 InRelease Obj:3 http://security.ubuntu.com/ubuntu focal-security InRelease Obj:4 http://dl.google.com/linux/chrome/deb stable InRelease Obj:5 http://ppa.launchpad.net/teejee2008/timeshift/ubuntu focal InRelease Des:6 http://archive.neon.kde.org/user focal InRelease [155 kB] Des:7 https://mega.nz/linux/MEGAsync/xUbuntu_20.04 ./ InRelease [2.441 B] Obj:8 http://packages.microsoft.com/repos/vscode stable InRelease Obj:9 http://es.archive.ubuntu.com/ubuntu focal InRelease Obj:10 http://es.archive.ubuntu.com/ubuntu focal-updates InRelease Obj:11 http://es.archive.ubuntu.com/ubuntu focal-backports InRelease Descargados 158 kB en 2s (91,5 kB/s) Leyendo lista de paquetes... Hecho
## Confirming "focal" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_12.x/dists/focal/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add - gpg: invalid key resource URL '/etc/apt/trusted.gpg.d/home:ColinDuquesnoy.gpg' gpg: recurso de bloque de claves '(null)': Error general gpg: key 7721F63BD38B4796: 2 firmas no comprobadas por falta de claves gpg: key E481C081DB2A84F7: 1 firma no comprobada por falta de una clave gpg: key E6D4736255751E5D: 1 firma no comprobada por falta de una clave gpg: key 3B4FE6ACC0B21F32: 3 firmas no comprobadas por falta de claves gpg: key D94AA3F0EFE21092: 3 firmas no comprobadas por falta de claves gpg: key 871920D1991BC93C: 1 firma no comprobada por falta de una clave gpg: Cantidad total procesada: 13 gpg: omitidas nuevas claves: 13 Error executing command, exiting
It’s in spanish, but basically means that it couldn’t check the signature, because keys are missing.
Any help would be appreciated, thanks.
OS: Linux Mint 18.3. Similar to Ubuntu.
As ever with Linux I don’t really know how I’m meant to go about installing software:
- is it already on the system? In this case yes, but it’s very old: 4.2.6. The current LTS version at time of writing is 10.16.3.
- should I use apt?
- should I use Software Manager?
- should I use a PPA?
- should I download a compressed file and extract?
Sofware Manager comments from other users are things like «go here for the latest version» (https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions)
The very first command there is
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
This fails:
>
mike@M17A ~ $ curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
[sudo] password for mike:
## Installing the NodeSource Node.js 10.x repo...
## Populating apt-get cache...
+ apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://dl.google.com/linux/chrome/deb stable Release
Hit:4 http://ppa.launchpad.net/adabbas/1stppa/ubuntu xenial InRelease
Get:5 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
... // then many messages like this:
Ign:42 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main all Packages
Ign:43 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main Translation-en_GB
Ign:44 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main Translation-en_GB
Ign:44 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main Translation-en
Fetched 329 kB in 23s (14.0 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4773BD5E130D1D45
W: The repository 'https://mirrors.evowise.com/mariadb/repo/10.1/ubuntu serena Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Failed to fetch http://repository.spotify.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4773BD5E130D1D45
E: Failed to fetch https://mirrors.evowise.com/mariadb/repo/10.1/ubuntu/dists/serena/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu/dists/serena/main/binary-amd64/Packages 404 Not Found
W: Some index files failed to download. They have been ignored, or old ones used instead.
Error executing command, exiting
… I’m not sure what all those mariadb commands are all about. I have MariaDB on my system and am worried that something there is the problem.
NB attempting the next command seems to indicate that this has failed:
mike@M17A ~ $ sudo apt-get install -y nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version (4.2.6~dfsg-1ubuntu4.2).
0 to upgrade, 0 to newly install, 0 to remove and 600 not to upgrade.
… i.e. the system still believes 4.2.6 is the latest version.
More generally, what precisely is the protocol for installing new software in Linux: is the above numbered list, 1 to 5, the right methodology? Using what order of priority for the method do experts install new software?
What I then tried
It seemed that failing sudo apt-get update was at the root of the problem.
Inspired by other questions I tried this:
sudo rm /var/lib/apt/lists/* -vf
followed by this:
sudo apt-get update
More lists of errors and warnings that don’t mean much to me:
...
Err:40 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main amd64 Packages
404 Not Found
Ign:41 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main i386 Packages
Ign:42 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main all Packages
Ign:43 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main Translation-en_GB
Ign:44 https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena/main Translation-en
Fetched 329 kB in 28s (11.6 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4773BD5E130D1D45
W: The repository 'https://mirrors.evowise.com/mariadb/repo/10.1/ubuntu serena Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Failed to fetch http://repository.spotify.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4773BD5E130D1D45
E: Failed to fetch https://mirrors.evowise.com/mariadb/repo/10.1/ubuntu/dists/serena/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu/dists/serena/main/binary-amd64/Packages 404 Not Found
W: Some index files failed to download. They have been ignored, or old ones used instead.
Later I tried the «manual installation» at the github page…
Failed in the same way:
mike@M17A ~ $ VERSION=node_10.16.3
mike@M17A ~ $ DISTRO="$(lsb_release -s -c)"
mike@M17A ~ $ echo "deb https://deb.nodesource.com/$VERSION $DISTRO main" | sudo tee /etc/apt/sources.list.d/nodesource.list
deb https://deb.nodesource.com/node_10.16.3 sylvia main
mike@M17A ~ $ echo "deb-src https://deb.nodesource.com/$VERSION $DISTRO main" | sudo tee -a /etc/apt/sources.list.d/nodesource.list
deb-src https://deb.nodesource.com/node_10.16.3 sylvia main
mike@M17A ~ $ sudo apt-get update
Hit:1 http://ppa.launchpad.net/adabbas/1stppa/ubuntu xenial InRelease
...
Ign:57 https://deb.opera.com/opera-stable stable/non-free Translation-en
Err:58 https://deb.opera.com/opera-stable stable/non-free amd64 Packages
503 Backend unavailable, connection timeout
Ign:59 https://deb.opera.com/opera-stable stable/non-free i386 Packages
Fetched 3,316 B in 34s (95 B/s)
Reading package lists... Done
W: The repository 'https://deb.nodesource.com/node_10.x sylvia Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4773BD5E130D1D45
W: The repository 'http://repository.spotify.com stable InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://mirrors.evowise.com/mariadb/repo/10.1/ubuntu serena Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu serena Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://deb.opera.com/opera-stable stable Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://deb.nodesource.com/node_10.x/dists/sylvia/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch https://mirrors.evowise.com/mariadb/repo/10.1/ubuntu/dists/serena/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch https://mirrors.evowise.com/mariadb/repo/10.2/ubuntu/dists/serena/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch https://deb.opera.com/opera-stable/dists/stable/non-free/binary-amd64/Packages 503 Backend unavailable, connection timeout
E: Some index files failed to download. They have been ignored, or old ones used instead.
The following command seems to be failing
curl -sL https://deb.nodesource.com/setup_10.x | bash —
Just says Error executing command, exiting.
Does anybody know how i can find out what the issue is?
root@294183bd6f26:/# curl -sL https://deb.nodesource.com/setup_10.x | bash -
## Installing the NodeSource Node.js 10.x repo...
## Populating apt-get cache...
+ apt-get update
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [94.3 kB]
Ign:2 http://deb.debian.org/debian stretch InRelease
Get:3 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [502 kB]
Get:6 http://deb.debian.org/debian stretch Release.gpg [2434 B]
Get:7 http://deb.debian.org/debian stretch-updates/main amd64 Packages [27.4 kB]
Get:8 http://deb.debian.org/debian stretch/main amd64 Packages [7082 kB]
Fetched 7918 kB in 2s (2958 kB/s)
Reading package lists... Done
## Installing packages required for setup: apt-transport-https lsb-release...
+ apt-get install -y apt-transport-https lsb-release > /dev/null 2>&1
Error executing command, exiting
asked Aug 29, 2019 at 9:32
- Печать
Страницы: [1] Вниз
Тема: Не устанавливается nvm,nodejs,npm (Прочитано 2243 раз)
0 Пользователей и 1 Гость просматривают эту тему.
makssun
Ubuntu чистая 16.04
Никакими способами не могу установить данные пакеты.
Инструкци отсюда брал:
http://www.hostingadvice.com/how-to/install-nodejs-ubuntu-14-04/
https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions
http://qaru.site/questions/11287/how-to-update-npm
curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
Fetched 2,959 kB in 2s (1,449 kB/s)
Reading package lists... Done
W: The repository 'http://ppa.launchpad.net/chris-lea/node.js/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://ppa.launchpad.net/chris-lea/node.js/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
Error executing command, exiting
sudo apt-get install nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version (4.2.6~dfsg-1ubuntu4.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@stone:~# node -v
-bash: node: command not found
sudo apt-get install npm
Reading package lists... Done
Building dependency tree... 50%
Building dependency tree
Reading state information... Done
npm is already the newest version (3.5.2-0ubuntu4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@stone:~#
root@stone:~# npm -v
/usr/bin/env: 'node': No such file or directory
nvm install 0.10.48
-bash: nvm: command not found
Где тут собака порылась?
ТС не появлялся на Форуме более полугода по состоянию на 22/07/2019 (последняя явка: 19/11/2018). Модератором раздела принято решение закрыть тему.
—zg_nico
« Последнее редактирование: 22 Июля 2019, 14:58:39 от zg_nico »
makssun
scsiman
makssun, репозиторий ppa:chris-lea/node.js нужно удалить (на каком сайте вы этот анахронизм вычитали?) и продолжить установку нормальным способом.
sudo add-apt-repository -r ppa:chris-lea/node.js
curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
Dell Studio XPS 16, Ubuntu 16.04 LTS (Home).
HP nx6110, Ubuntu 8.04 LTS => 10.04 LTS (Home).
makssun
Так, это помогло, но nvm почему не устанавливается?
node -v
v8.11.1
root@stone:/home/max# npm -v
5.8.0
root@stone:/home/max# nvm ls
-bash: nvm: command not found
root@stone:/home/max# nvm install 0.10.48
-bash: nvm: command not found
scsiman
makssun, Несколько версий node.js одновременно надо установить? Если нет, то nvm не нужен.
Dell Studio XPS 16, Ubuntu 16.04 LTS (Home).
HP nx6110, Ubuntu 8.04 LTS => 10.04 LTS (Home).
makssun
Спасибо, просто в инструкции так сказано, делаю, а оно не устанавливается.
Собственно, почему?
scsiman
makssun, не все инструкции одинаково полезны.
Обычно автор инструкции предполагает, что пользователь хотя бы примерно понимает, что и как он делает.
Dell Studio XPS 16, Ubuntu 16.04 LTS (Home).
HP nx6110, Ubuntu 8.04 LTS => 10.04 LTS (Home).
- Печать
Страницы: [1] Вверх
Hello I wonder if anyone knows what is happening here before I install on to Jesse manually and kill all chances of updates later on. There are guides on how to install Homebridge on Jesse Lite on a Raspberry Pi 2 manually but the advice is to try with apt-get update. It would be a good learn if I can find out what is wrong I think so here goes (My comments are in brackets):
RaspBerry Pi 2 with Raspbian Lite — Raspbian GNU/Linux 8 n l downloaded and installed today
sudo apt-get update
sudo apt-get upgrade
pi@raspberrypi:~ $ which git
/usr/bin/git
pi@raspberrypi:~ $ which make
/usr/bin/make
g++-4.9 -v = gcc version 4.9.2 (Raspbian 4.9.2-10)
(So C++ installed)
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.4.50-v7+ *************************** armv7l GNU/Linux
(so arm7 processor so nodejs should install with apt-get)
sudo apt-get install -y nodejs
(Checked installation)
pi@raspberrypi:~ $ nodejs —version
v0.10.29
sudo apt-get install libavahi-compat-libdnssd-dev
(Then tried to install Homebridge)
sudo npm install -g —unsafe-perm homebridge
(Didn’t understand npm so:)
sudo apt-get install npm
(Then tried to install Homebridge)
sudo npm install -g —unsafe-perm homebridge
(Get the following when I try the Homebridge install:)
BASH
pi@raspberrypi:~ $ sudo npm install -g --unsafe-perm homebridge npm WARN engine homebridge@0.4.20: wanted: {"node":">=4.3.2"} (current: {"node":"0.10.29","npm":"1.4.21"}) npm WARN engine hap-nodejs@0.4.25: wanted: {"node":">=4.3.2"} (current: {"node":"0.10.29","npm":"1.4.21"}) - > curve25519-n2@1.1.3 install /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519-n2 > node-gyp rebuild /bin/sh: 1: node: not found gyp: Call to 'node -e "require('nan')"' returned exit status 127. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:344:16) gyp ERR! stack at ChildProcess.emit (events.js:98:17) gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:809:12) gyp ERR! System Linux 4.4.50-v7+ gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild" gyp ERR! cwd /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519-n2 gyp ERR! node -v v0.10.29 gyp ERR! node-gyp -v v0.12.2 gyp ERR! not ok npm WARN This failure might be due to the use of legacy binary "node" npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian > mdns@2.3.3 install /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns > node-gyp rebuild node.js:815 var cwd = process.cwd(); ^ Error: ENOENT, no such file or directory at Function.startup.resolveArgv0 (node.js:815:23) at startup (node.js:58:13) at node.js:906:3 npm WARN This failure might be due to the use of legacy binary "node" npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian > ed25519@0.0.4 install /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/ed25519 > node-gyp rebuild pi@raspberrypi:~ $
Does anyone know what is missing here at all and if there is an easy fix. Any help greatly appreciated.