21

I have some Ubuntu Server 20.04 installations, but just for one of them happens the following:

sudo apt update
... password
Hit:1 http://repo.mysql.com/apt/ubuntu groovy InRelease
Ign:2 http://pe.archive.ubuntu.com/ubuntu groovy InRelease
Ign:3 http://pe.archive.ubuntu.com/ubuntu groovy-updates InRelease
Hit:4 http://apt.postgresql.org/pub/repos/apt groovy-pgdg InRelease
Ign:5 http://pe.archive.ubuntu.com/ubuntu groovy-backports InRelease
Ign:6 http://pe.archive.ubuntu.com/ubuntu groovy-security InRelease
Err:7 http://pe.archive.ubuntu.com/ubuntu groovy Release
  404  Not Found [IP: 200.236.31.4 80]
Err:8 http://pe.archive.ubuntu.com/ubuntu groovy-updates Release
  404  Not Found [IP: 200.236.31.4 80]
Err:9 http://pe.archive.ubuntu.com/ubuntu groovy-backports Release
  404  Not Found [IP: 200.236.31.4 80]
Err:10 http://pe.archive.ubuntu.com/ubuntu groovy-security Release
  404  Not Found [IP: 200.236.31.4 80]
Reading package lists... Done
E: The repository 'http://pe.archive.ubuntu.com/ubuntu groovy Release' no longer has 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://pe.archive.ubuntu.com/ubuntu groovy-updates Release' no longer has 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://pe.archive.ubuntu.com/ubuntu groovy-backports Release' no longer has 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://pe.archive.ubuntu.com/ubuntu groovy-security Release' no longer has 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.

What happened this? and how to solve?

2 Answers2

11

In my case, I had several Ubuntu 20.10 Docker images running on my server. Due to the deprecation of Ubuntu 20.10, all of the PPA releases are gone.
I solved it by deploying Ubuntu 20.04 images instead and updating the packages for that version. I plan on deploying new images at 22.04, once that's been out for a while.

From experience, even though it's possible, it's not recommended to try downgrading the packages and PPA on your machine.

While this is generally a duplicate of What can I do if a repository/PPA does not have a Release file?, this is specific to Ubuntu deprecating versions in a generally unexpected manner.

0

use following repositories:

deb http://archive.ubuntu.com/ubuntu/ focal main restricted
deb http://archive.ubuntu.com/ubuntu/ focal-updates main restricted
deb http://archive.ubuntu.com/ubuntu/ focal universe
deb http://archive.ubuntu.com/ubuntu/ focal-updates universe
deb http://archive.ubuntu.com/ubuntu/ focal multiverse
deb http://archive.ubuntu.com/ubuntu/ focal-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu focal-security main restricted
deb http://security.ubuntu.com/ubuntu focal-security universe
deb http://security.ubuntu.com/ubuntu focal-security multiverse

replace all groovy to focal in sources.list it works me!

M2E67
  • 109