| From: | Fernan Aguero <fernan(dot)aguero(at)gmail(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org> |
| Cc: | pgsql-pkg-debian(at)lists(dot)postgresql(dot)org |
| Subject: | Re: problem running apt update on jammy (InRelease is not signed) |
| Date: | 2026-04-28 12:41:19 |
| Message-ID: | CAC62LX69Rp-3H-g542Y6a4JBoh6e0fMYBC_Oi9B18DAZHDn7vw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)debian(dot)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 //
| From | Date | Subject | |
|---|---|---|---|
| Next Message | apt.postgresql.org Repository Update | 2026-04-28 21:36:50 | timescaledb updated to version 2.26.4+dfsg-1.pgdg+1 |
| Previous Message | Christoph Berg | 2026-04-28 12:08:04 | Re: problem running apt update on jammy (InRelease is not signed) |