Re: Update Old Version Public Keys?

On Mon, Oct 12, 2020 at 4:28 PM Christoph Berg <myon(at)debian(dot)org> wrote:

> Re: David E. Wheeler
> > > Okay, I changed it to:
> > >
> > > ```
> > > ADD
> https://salsa.debian.org/postgresql/postgresql-common/-/raw/master/pgdg/apt.postgresql.org.sh
> /usr/local/bin/
>
> > Hello gang. I tried this again today, now that 13.0 is out, and get the
> same errors. Do I need to do something different than I did for 12 and
> earlier? Example:
> >
> > https://github.com/theory/pg-semver/runs/1239421317
>
> | + apt.postgresql.org.sh -p -v 13
> | This script will enable the PostgreSQL APT repository on
> apt.postgresql.org on
> | your system. The distribution codename used will be buster-pgdg-testing.
>
> Is that the latest version of the apt.postgresql.org.sh script? It
> should only use "-testing" when passed -t.
>
> Christoph
>

I think the issue (in part) is here:
https://salsa.debian.org/postgresql/postgresql-common/-/blob/master/pgdg/apt.postgresql.org.sh#L77-85

Because `-v 13` called in the script above forces the 'testing' release,
installation will fail since the pgxn docker image's 'pg-start' script
doesn't re-pin the release priority to include 'testing':
https://github.com/pgxn/docker-pgxn-tools/blob/main/bin/pg-start#L12

Both should be updated; the former updated to realize the release of
PostgreSQL 13 in non-testing repositories, and the latter to enable pinning
of the testing release when necessary.

-- Aaron