apt-get update fails on Ubuntu1604 image
Hi,
My build today fails at the very start during sudo apt-get update
on an Ubuntu1604 image. It seems that the apt.postgresql.org repository is at fault. The interesting bits are:
Ign:28 http://apt.postgresql.org/pub/repos/apt xenial-pgdg/main Translation-en
Err:30 http://apt.postgresql.org/pub/repos/apt xenial-pgdg/main amd64 Packages
404 Not Found [IP: 147.75.85.69 80]
Ign:32 http://apt.postgresql.org/pub/repos/apt xenial-pgdg/main i386 Packages
Get:38 http://ppa.launchpad.net/git-core/ppa/ubuntu xenial/main amd64 Packages [3340 B]
Get:39 http://ppa.launchpad.net/git-core/ppa/ubuntu xenial/main i386 Packages [3348 B]
Get:40 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1093 B]
Get:41 https://packages.microsoft.com/ubuntu/16.04/prod xenial/main amd64 Packages [291 kB]
Fetched 4207 kB in 6s (651 kB/s)
Reading package lists... Done
: The repository 'http://apt.postgresql.org/pub/repos/apt xenial-pgdg 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://apt.postgresql.org/pub/repos/apt/dists/xenial-pgdg/main/binary-amd64/Packages 404 Not Found [IP: 147.75.85.69 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
Command exited with code 100
It seems that the support for xenial has been removed from Postgresql : https://wiki.postgresql.org/wiki/Apt#News
I don't use the service but other people might be affected.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Feodor Fitsner on 19 Sep, 2022 05:52 PM
Thanks for letting know! Will update the image shortly.
2 Posted by Mu Masri on 22 Sep, 2022 09:49 PM
Hi, we got the same error and using xenial packages. any idea how to workaround this? also, is there an estimation for a stable fix for this?
Support Staff 3 Posted by Feodor Fitsner on 23 Sep, 2022 12:28 AM
The workaround is to add the following command to before
sudo apt update
:Feodor Fitsner closed this discussion on 23 Nov, 2022 09:02 PM.