Re: problem running apt update on jammy (InRelease is not signed) - Mailing list pgsql-pkg-debian

From Fernan Aguero
Subject Re: problem running apt update on jammy (InRelease is not signed)
Date
Msg-id CAC62LX69Rp-3H-g542Y6a4JBoh6e0fMYBC_Oi9B18DAZHDn7vw@mail.gmail.com
Whole thread
In response to Re: problem running apt update on jammy (InRelease is not signed)  (Christoph Berg <myon@debian.org>)
List pgsql-pkg-debian
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 // 


pgsql-pkg-debian by date:

Previous
From: Christoph Berg
Date:
Subject: Re: problem running apt update on jammy (InRelease is not signed)
Next
From: apt.postgresql.org Repository Update
Date:
Subject: timescaledb updated to version 2.26.4+dfsg-1.pgdg+1