Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last month.
Improve this question
I have seen some similar questions, but in my case the following error popped up when I ran sudo apt-get update:
ICON_lab) randychen#randychen-Delta-15-A5EFK:~/projects$ sudo apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
Ign:3 http://packages.ros.org/ros/ubuntu jammy InRelease
Err:4 http://packages.ros.org/ros/ubuntu jammy Release
404 Not Found [IP: 140.211.166.134 80]
Get:5 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Get:6 http://www.deb-multimedia.org jessie InRelease [15.4 kB]
Hit:7 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:8 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:9 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [95.1 kB]
Get:10 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [257 kB]
Get:11 http://us.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
Get:13 http://us.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [11.4 kB]
Ign:6 http://www.deb-multimedia.org jessie InRelease
Hit:12 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Reading package lists... Done
E: The repository 'http://packages.ros.org/ros/ubuntu jammy 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://www.deb-multimedia.org jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5C808C2B65558117
E: Release file for http://www.deb-multimedia.org/dists/jessie/InRelease is expired (invalid since 388d 20h 52min 20s). Updates for this repository will not be applied.
W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
At first I thought it's due to a PPA but I don't have any here. I tried trouble shooting it by following this post, and I added that line of code on the top of the file, but it's not working either.
Any help is greatly appreciated!
You have to correct the url:
sudo grep -rlF 'http://packages.ros.org' /etc/apt/sources* |
xargs sed -i 's#http://packages.ros.org#https://ubuntu.osuosl.org/#'
sudo apt update
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 10 months ago.
Improve this question
Running:
docker run -it ubuntu:22.04 /bin/bash
apt update
Fails with:
22.04: Pulling from library/ubuntu
Digest: sha256:7599221e4e2e4eeb90ad282fc523139578f3dfea245b5049c4fee1b28776d2be
Status: Downloaded newer image for ubuntu:22.04
root#117960ca68dd:/# apt update
Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [90.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [90.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [90.7 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB]
Get:6 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1792 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [266 kB]
Get:8 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [164 kB]
Fetched 20.2 MB in 2s (9747 kB/s)
Reading package lists... Done
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
E: Sub-process returned an error code
Pulling ubuntu:21.10 still works fine.
What is causing this and how can it be avoided?
Been using docker:latest since over a year and 1st time things completely broke down during a new deploy due to the assumption that an official docker image 'just works'.
I wanna remove all these error and get back to a clean message. But I don't know how to remove these.
sudo apt update
Hit:1 http://packages.microsoft.com/repos/code stable InRelease
Hit:2 http://ppa.launchpad.net/linuxuprising/java/ubuntu focal InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease
Ign:4 http://ppa.launchpad.net/webupd8team/java/ubuntu focal InRelease
Hit:5 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:7 https://download.sublimetext.com apt/stable/ InRelease
Get:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Err:9 http://ppa.launchpad.net/webupd8team/java/ubuntu focal Release
404 Not Found [IP: 2001:67c:1560:8008::19 80]
Get:10 http://archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/webupd8team/java/ubuntu focal 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.
The key to the real problem can be found on this line - E: The repository 'http://ppa.launchpad.net/webupd8team/java/ubuntu focal Release' does not have a Release file.
You need to clean the PPA to get rid of the error. Thankfully, someone explained how to do that, here - https://askubuntu.com/questions/866901/what-can-i-do-if-a-repository-ppa-does-not-have-a-release-file
I've had, in the past, gdal utilities installed successfully on a Databricks Cluster running 20.04.3 LTS (focal).
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
$ sudo apt-get install -y gdal-bin
Each time a databricks job cluster startups, my sample notebook attempts to install GDAL. I've attempted a series of apt-get updates/upgrades; and just when I think the issue has gone away; the next day it comes back again (no change of code, cluster spec, etc.)
Most recently the issue occurs once it hits installation for libmysqlclient21, e.g:
Err:27 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libmysqlclient21 amd64 8.0.26-0ubuntu0.20.04.3
404 Not Found [IP: 91.189.88.142 80]
My understanding is that these issues arise when the packaging versions are no longer supported, and noticed that libmysqlclient21 has come out with a recent patch as of the 25th of October (when the issue started arising).
I've noticed when I run %sh sudo apt-get --fix-missing -y update and apt policy libmysqlclient21, prior to a successful installation, I can see it's found 8.0.27-0ubuntu0.20.04.1:
Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:3 https://repos.azul.com/zulu/deb stable InRelease
Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:5 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [628 kB]
Get:6 http://archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Get:7 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [1,635 kB]
Get:8 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [801 kB]
Get:9 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [1,183 kB]
Get:10 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1,086 kB]
Get:11 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [33.4 kB]
Get:12 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [679 kB]
Fetched 6,374 kB in 19s (329 kB/s)
Reading package lists...
libmysqlclient21:
Installed: (none)
Candidate: 8.0.27-0ubuntu0.20.04.1
Version table:
8.0.27-0ubuntu0.20.04.1 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
8.0.19-0ubuntu5 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
On an unsuccessful run, it's returning:
Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:3 https://repos.azul.com/zulu/deb stable InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Reading package lists...
libmysqlclient21:
Installed: (none)
Candidate: 8.0.26-0ubuntu0.20.04.3
Version table:
8.0.26-0ubuntu0.20.04.3 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
8.0.26-0ubuntu0.20.04.2 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
8.0.19-0ubuntu5 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
I've been scratching my head trying to understand what could be causing this, and what else to do to work around the problem. I'd prefer it to handle the installation automatically without having to hardcode specific versions (in case other issues were to arise); but not against targeting specific versions if I know they'll be supported on the current platform.
Any advice appreciated.
I had success by putting
sudo apt clean && sudo apt update --fix-missing -y && sudo apt install -y libmysqlclient21
before trying to install gdal and it seems to be working now....
...nevermind began failing the next day again...
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Hi guys i'm having the following problem running sudo apt-get update, any clues on what might be causing this?
sudo apt-get update
Hit:1 http://linux.teamviewer.com/deb stable InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:3 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:5 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:6 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu bionic InRelease
Hit:7 http://packages.microsoft.com/repos/vscode stable InRelease
Hit:9 http://apt.postgresql.org/pub/repos/apt bionic-pgdg InRelease
Hit:8 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Err:10 http://br.archive.ubuntu.com/ubuntu bionic InRelease
Could not connect to br.archive.ubuntu.com:80 (200.236.31.4). - connect (113: No route to host)
Err:11 http://br.archive.ubuntu.com/ubuntu bionic-updates InRelease
Unable to connect to br.archive.ubuntu.com:http:
Err:12 http://br.archive.ubuntu.com/ubuntu bionic-backports InRelease
Unable to connect to br.archive.ubuntu.com:http:
Reading package lists... Done
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/bionic/InRelease Could not connect to br.archive.ubuntu.com:80 (200.236.31.4). - connect (113: No route to host)
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Unable to connect to br.archive.ubuntu.com:http:
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Unable to connect to br.archive.ubuntu.com:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.
The br archive server for ubuntu is throwing 504 errors right now, either wait or change the text http://br.archive.ubuntu.com/ubuntu in /etc/apt/sources.list to http://archive.ubuntu.com/ubuntu.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I have tried installing NodeJS by using the following command:
sudo apt-get install nodejs
The problem is, it installs an older version of NodeJS. So I found another way to install a newer version of NodeJS by the following command:
curl -sL https://deb.nodesource.com/setup_9.x | sudo -E bash -
But it keeps throwing me the following error message:
adam#adam-pc:~$ curl -sL https://deb.nodesource.com/setup_9.x | sudo -E bash -
## Installing the NodeSource Node.js v9.x repo...
## Populating apt-get cache...
+ apt-get update
Get:1 http://hu.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Hit:2 http://ppa.launchpad.net/git-core/ppa/ubuntu xenial InRelease
Get:3 http://hu.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Ign:4 http://dl.google.com/linux/chrome/deb stable InRelease
Get:5 http://hu.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Hit:6 http://ppa.launchpad.net/linrunner/tlp/ubuntu xenial InRelease
Hit:7 http://dl.google.com/linux/chrome/deb stable Release
Ign:8 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial InRelease
Hit:9 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:10 http://ppa.launchpad.net/webupd8team/sublime-text-3/ubuntu xenial InRelease
Ign:11 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial Release
Ign:12 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 Packages
Ign:13 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main i386 Packages
Ign:14 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main all Packages
Ign:15 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en_US
Ign:16 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en
Ign:17 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:18 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main DEP-11 64x64 Icons
Ign:12 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 Packages
Ign:13 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main i386 Packages
Ign:14 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main all Packages
Ign:15 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en_US
Ign:16 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en
Ign:17 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:18 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main DEP-11 64x64 Icons
Ign:12 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 Packages
Ign:13 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main i386 Packages
Ign:14 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main all Packages
Ign:15 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en_US
Ign:16 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en
Ign:17 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:18 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main DEP-11 64x64 Icons
Ign:12 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 Packages
Ign:13 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main i386 Packages
Ign:14 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main all Packages
Ign:15 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en_US
Ign:16 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en
Ign:17 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:18 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main DEP-11 64x64 Icons
Ign:12 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 Packages
Ign:13 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main i386 Packages
Ign:14 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main all Packages
Ign:15 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en_US
Ign:16 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en
Ign:17 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:18 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main DEP-11 64x64 Icons
Err:12 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 Packages
404 Not Found
Ign:13 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main i386 Packages
Ign:14 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main all Packages
Ign:15 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en_US
Ign:16 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main Translation-en
Ign:17 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:18 http://ppa.launchpad.net/michael-gruz/canon-trunk/ubuntu xenial/main DEP-11 64x64 Icons
Fetched 451 kB in 6s (70,4 kB/s)
Reading package lists... Done
W: The repository 'http://ppa.launchpad.net/michael-gruz/canon-trunk/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/michael-gruz/canon-trunk/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
I keep looking for a solution for hours now, tried around 10 ideas from StackOverflow and from different forums that I found on Google, but still nothing.
EDIT:
Meanwhile I found the solution.
I opened Ubuntu Update manager by the following command:
update-manager
Then I clicked on Settings and Other software tab and unticked all the http://ppa.launchpad.net/ stuff I found ticked and strange (especially all the michael-gruz links).
Then used the commands above again:
curl -sL https://deb.nodesource.com/setup_9.x | sudo -E bash -
sudo apt-get install nodejs
Now I got v9.5.0 installed.
There's nothing wrong with that install command itself. If you were to look why it errors out, you can see that a launchpad package has gone 404. If you remove this repository, it won't interrupt apt and allow installing the package. You should be able to remove this removed PPA like so:
sudo add-apt-repository --remove ppa:michael-gruz/ppa
I recommend to use a version manager for node. The most popular ones are nvm and n.
Now you can:
sudo apt-get install nodejs // install a really old node
npm install n -g // get n
n latest // get latest node, or a specific one with n v8.0.0