Обсуждение: problem running apt update on jammy (InRelease is not signed)
Hi all,
I am running into this problem with apt in Ubuntu jammy (22.04 LTS), see error message below. Not sure how to fix this or work around this.
I have followed all guidelines on https://wiki.postgresql.org/wiki/Apt, the certificates are up to date. I also removed outdated apt lists, but it was to no avail.
I'd appreciate any help resolving this. Thanks!
# sudo rm /var/lib/apt/lists/*
# sudo apt update
[...]
Get:10 https://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease [180 kB]
Err:10 https://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease
Splitting up /var/lib/apt/lists/partial/apt.postgresql.org_pub_repos_apt_dists_jammy-pgdg_InRelease into data and signature failed
Err:10 https://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease
Splitting up /var/lib/apt/lists/partial/apt.postgresql.org_pub_repos_apt_dists_jammy-pgdg_InRelease into data and signature failed
[...]
Reading package lists... DoneW: GPG error: https://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease: Splitting up /var/lib/apt/lists/partial/apt.postgresql.org_pub_repos_apt_dists_jammy-pgdg_InRelease into data and signature failed
E: The repository 'https://apt.postgresql.org/pub/repos/apt jammy-pgdg 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.
# sudo cat /etc/apt/sources.list.d/pgdg.sources
Types: deb
URIs: https://apt.postgresql.org/pub/repos/apt
Suites: jammy-pgdg
Components: main
Signed-By: /etc/apt/trusted.gpg.d/apt.postgresql.org.asc
URIs: https://apt.postgresql.org/pub/repos/apt
Suites: jammy-pgdg
Components: main
Signed-By: /etc/apt/trusted.gpg.d/apt.postgresql.org.asc
# sudo find /etc/apt/ -iname '*postgresql*'
/etc/apt/apt.conf.d/02autoremove-postgresql
/etc/apt/trusted.gpg.d/postgresql.gpg
/etc/apt/trusted.gpg.d/apt.postgresql.org.asc
/etc/apt/trusted.gpg.d/apt.postgresql.org.gpg
/etc/apt/apt.conf.d/02autoremove-postgresql
/etc/apt/trusted.gpg.d/postgresql.gpg
/etc/apt/trusted.gpg.d/apt.postgresql.org.asc
/etc/apt/trusted.gpg.d/apt.postgresql.org.gpg
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy
fernan
// Don't it always seem to go,
that you don't know what you've got
till it's gone
They paved paradise
and put up a parking lot.
-- Joni Mitchell //
Вложения
Re: Fernan Aguero > I have followed all guidelines on https://wiki.postgresql.org/wiki/Apt, the > certificates are up to date. I also removed outdated apt lists, but it was > to no avail. Hi Fernan, the file you attached is from 10 Jan 2026. Is there any caching proxy involved like approx, apt-cacher or the like? Christoph
Thanks Christoph for chiming in,
you're right, didn't notice the date. We're behind our university firewall + cloudflare (proxy). Not sure what to do next. I will ask our IT department to look into it. It's strange that this did not happen to other repos sourced by apt (e.g. CRAN, docker, github, nvidia ...), the only one failing is postgres.
I will be back hopefully with a solution. Thanks again -- fernan
On Tue, Apr 28, 2026 at 9:08 AM Christoph Berg <myon@debian.org> wrote:
Re: Fernan Aguero
> I have followed all guidelines on https://wiki.postgresql.org/wiki/Apt, the
> certificates are up to date. I also removed outdated apt lists, but it was
> to no avail.
Hi Fernan,
the file you attached is from 10 Jan 2026. Is there any caching proxy
involved like approx, apt-cacher or the like?
Christoph
fernan
// Don't it always seem to go,
that you don't know what you've got
till it's gone
They paved paradise
and put up a parking lot.
-- Joni Mitchell //