public inbox for [email protected]  

help / color / mirror / Atom feed
From: Fernan Aguero <[email protected]>
To: Christoph Berg <[email protected]>
Cc: [email protected]
Subject: Re: problem running apt update on jammy (InRelease is not signed)
Date: Tue, 28 Apr 2026 09:41:19 -0300
Message-ID: <CAC62LX69Rp-3H-g542Y6a4JBoh6e0fMYBC_Oi9B18DAZHDn7vw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAC62LX5sb+saA4WQnBF+bhe4R1T3Ft+V=NzX7k6Q-KMWBfMdqQ@mail.gmail.com>
	<[email protected]>

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 <[email protected]> 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 //


reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: problem running apt update on jammy (InRelease is not signed)
  In-Reply-To: <CAC62LX69Rp-3H-g542Y6a4JBoh6e0fMYBC_Oi9B18DAZHDn7vw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox