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 3 years ago.
Improve this question
Problem: impossible to execute 'apt-get update' (Ubuntu 18.10)
Ubuntu 18.10 cosmic end of life
I tried to upgrade my system version but i got the same error of apt-get update command
$ apt update
Ign:1 http://archive.ubuntu.com/ubuntu cosmic InRelease
Ign:2 http://security.ubuntu.com/ubuntu cosmic-security InRelease
Ign:3 http://archive.ubuntu.com/ubuntu cosmic-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu cosmic-backports InRelease
Err:5 http://security.ubuntu.com/ubuntu cosmic-security Release
404 Not Found [IP: 91.189.88.173 80]
Err:6 http://archive.ubuntu.com/ubuntu cosmic Release
404 Not Found [IP: 91.189.88.31 80]
Err:7 http://archive.ubuntu.com/ubuntu cosmic-updates Release
404 Not Found [IP: 91.189.88.31 80]
Err:8 http://archive.ubuntu.com/ubuntu cosmic-backports Release
404 Not Found [IP: 91.189.88.31 80]
Reading package lists... Done
E: The repository 'http://security.ubuntu.com/ubuntu cosmic-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://archive.ubuntu.com/ubuntu cosmic 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://archive.ubuntu.com/ubuntu cosmic-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.
E: The repository 'http://archive.ubuntu.com/ubuntu cosmic-backports 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.
Related
I'm trying to update my server with apt-get update and this error shows up...
My Server runs on Ubuntu 18.04
Ign:1 https://packages.sury.org/php bionic InRelease
Err:2 https://packages.sury.org/php bionic Release
404 Not Found [IP: 138.199.37.227 443]
Ign:3 http://old-releases.ubuntu.com/ubuntu bionic InRelease
Hit:4 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
Ign:5 http://old-releases.ubuntu.com/ubuntu bionic-updates InRelease
Ign:6 http://old-releases.ubuntu.com/ubuntu bionic-security InRelease
Err:7 http://old-releases.ubuntu.com/ubuntu bionic Release
404 Not Found [IP: 185.125.190.40 80]
Err:8 http://old-releases.ubuntu.com/ubuntu bionic-updates Release
404 Not Found [IP: 185.125.190.40 80]
Err:9 http://old-releases.ubuntu.com/ubuntu bionic-security Release
404 Not Found [IP: 185.125.190.40 80]
Hit:10 https://packagecloud.io/pufferpanel/pufferpanel/ubuntu bionic InRelease
Reading package lists... Done
E: The repository 'https://packages.sury.org/php 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 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.
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.
Does anybody know how i can fix that?
It looks like you are using repositories that do not contain this version of ubuntu (http://old-releases.ubuntu.com/ubuntu) and others designed for Debian (https://packages.sury.org/php).
I recommend you edit your /etc/apt/sources.list file, replace the content with the one you can find in this repository and then try with:
apt update
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
I run sudo apt-get update then I get this error
Hit:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 https://deb.nodesource.com/node_16.x focal InRelease
Err:3 http://ph.archive.ubuntu.com/ubuntu focal InRelease
403 Forbidden [IP: 202.79.184.254 80]
Err:4 http://ph.archive.ubuntu.com/ubuntu focal-updates InRelease
403 Forbidden [IP: 202.79.184.254 80]
Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
Err:6 http://ph.archive.ubuntu.com/ubuntu focal-backports InRelease
403 Forbidden [IP: 202.79.184.254 80]
Hit:7 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease
Hit:8 http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu focal InRelease
Hit:9 http://ppa.launchpad.net/sylvain-pineau/kazam/ubuntu focal InRelease
Reading package lists... Done
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
E: The repository 'http://ph.archive.ubuntu.com/ubuntu focal InRelease' is not signed.
E: Failed to fetch http://ph.archive.ubuntu.com/ubuntu/dists/focal/InRelease 403 Forbidden [IP: 202.79.184.254 80]
E: Failed to fetch http://ph.archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease 403 Forbidden [IP: 202.79.184.254 80]
E: The repository 'http://ph.archive.ubuntu.com/ubuntu focal-updates 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.
E: Failed to fetch http://ph.archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease 403 Forbidden [IP: 202.79.184.254 80]
E: The repository 'http://ph.archive.ubuntu.com/ubuntu focal-backports 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.
I tried searching everywhere and checked related topics but none seems working.
How do I resolve this?
I have passed through the same problem. The solution was to change my internet connection. The problem seem to have been the firewalls in my corporation network that gave me the same exact messages, including the IP address that you've pasted.
I changed my network connection to a different one and that worked for me. I think firewall of the first network disabled updates to save bandwidths or something like that.
Had the same error but with a different repository.
Try this out if it works for you.
ls /etc/apt/sources.list.d
listing the repositories.
rm -i /etc/apt/sources.list.d/output of 1
Then of course run.
apt upgrade
More details in the screenshots in these links.
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 1 year ago.
Improve this question
I'm using Docker desktop v2.3.0 and I enabled WSL2 on Windows 10 Professional v1909.
I installed Ubuntu 20.04 distribution, I accessed it and when I run apt-get update:
Err:1 http://archive.ubuntu.com/ubuntu focal InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu focal-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
I tried to update the /etc/resolve.conf by adding the company dns server after using ipconfig /all.
Then I rebooted the WSL but does not work.
I found a similar question No internet connection on WSL Ubuntu (Windows Subsystem for Linux) and tried this solution but none of them fixed the issue for me.
I use a proxy to access the internet, can it forbid the WSL from accessing the external network and should add it the wsl config file?
While running the sudo apt-get update on ubuntu 17.04 Zesty Zapus, I am getting the following error. I have posted on the error lines. I wanted to install python libraries like matplotlib and tkinter which failed to installed because above command wasn't running succesfully. Please suggest me what to do.
Err:9 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages
404 Not Found [IP: 2001:67c:1560:8001::14 80]
Err:25 http://in.archive.ubuntu.com/ubuntu zesty/main i386 Packages
404 Not Found [IP: 2001:67c:1360:8001::21 80]
Err:81 http://in.archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages
404 Not Found [IP: 2001:67c:1360:8001::21 80]
Err:113 http://in.archive.ubuntu.com/ubuntu zesty-backports/main amd64 Packages
404 Not Found [IP: 2001:67c:1360:8001::21 80]
Reading package lists... Done
W: The repository 'http://security.ubuntu.com/ubuntu zesty-security 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 'http://in.archive.ubuntu.com/ubuntu zesty 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 'http://in.archive.ubuntu.com/ubuntu zesty-updates 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 'http://in.archive.ubuntu.com/ubuntu zesty-backports 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://security.ubuntu.com/ubuntu/dists/zesty-security/main/binary-amd64/Packages 404 Not Found [IP: 2001:67c:1560:8001::14 80]
E: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/zesty/main/binary-i386/Packages 404 Not Found [IP: 2001:67c:1360:8001::21 80]
E: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/zesty-updates/main/binary-amd64/Packages 404 Not Found [IP: 2001:67c:1360:8001::21 80]
E: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/zesty-backports/main/binary-amd64/Packages 404 Not Found [IP: 2001:67c:1360:8001::21 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
you can solve it by: just replace us.archive.ubuntu.com and security.ubuntu.com in /etc/apt/sources.list with old-releases.ubuntu.com and then you'll be able to finish updating.
refer to source 1 and ubuntu forum
it work for me
In my case:
sed -e 's/archive.ubuntu.com/old-releases.ubuntu.com/g' -i /etc/apt/sources.list
sed -e 's/security.ubuntu.com/old-releases.ubuntu.com/g' -i /etc/apt/sources.list
In my case, I was able to download some of the packages by doing the following:
I had to replace "us.archive.ubuntu.com" and "security.ubuntu.com" in /etc/apt/sources.list WITH "old-releases.ubuntu.com" and then I was able to finish downloading some of the packages, like Ayush Kumar said.
For the other updates that were listed by my Hosting company, Linode, I used the following:
I had to use the --allow-unauthenticated flag with sudo apt-get update.
sudo apt-get update --allow-unauthenticated
Then I was able to finish updating.
17.04 isn't getting further support from Ubuntu. So, the solution that worked for me was to upgrade it to 17.10 as none other solutions helped.