Re: Update Old Version Public Keys?

On Sat, Oct 17, 2020 at 6:30 PM David E. Wheeler <david(at)justatheory(dot)com>
wrote:

> On Oct 13, 2020, at 14:44, Christoph Berg <myon(at)debian(dot)org> wrote:
>
> >> Now, if I wanted to test Postgres 14 (dev), what additional steps would
> I have to take?
> >
> > sudo /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh -v 14 -i
>
> For some reason it doesn’t work:
>
>
> https://github.com/theory/pg-semver/runs/1269694601?check_suite_focus=true
>
> That’s running
>
> PGVERSION=14
> apt.postgresql.org.sh -p -v $PGVERSION
> packages="postgresql-$PGVERSION postgresql-server-dev-$PGVERSION
> postgresql-common"
> apt-get -o Dpkg::Options::="--force-confdef" -o
> Dpkg::Options::="--force-confold" install -y $packages
>
> Working fine on v13 and earlier.
>
> Thanks,
>
> David
>

This is back to the release pin priority issue. PG14 is only available in
the testing release, and the testing release's pin priority does not permit
use without explicit enabling, i.e., use of apt-get option `-t
<release-codename>-pgdg-testing`.

Alternatively, skip the `apt-get` and simply use apt.postgresql.org.sh's
`-i` option to install, if you can accept it overwriting any existing
PostgreSQL configuration files, since it would achieve the same package set
installation goal.

-- Aaron