public inbox for [email protected]help / color / mirror / Atom feed
Update Old Version Public Keys? 18+ messages / 3 participants [nested] [flat]
* Update Old Version Public Keys? @ 2020-06-07 16:47 David E. Wheeler <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-06-07 16:47 UTC (permalink / raw) To: pgsql-pkg-debian Hello Apters, I noticed while making tests for an extension that supports older versions of PostgreSQL that the public keys for the 8.4 and 9.1 (but not 9.0) repos are out-of-date. Some details here: https://github.com/docker-library/postgres/issues/737 Any chance they could be updated? I realize that the community had dropped support for 9.4 and earlier, but as long as there are repos, perhaps the keys should be kept up-to-date? Thanks, David Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-06-08 14:28 Christoph Berg <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: Christoph Berg @ 2020-06-08 14:28 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; +Cc: pgsql-pkg-debian Re: David E. Wheeler > Hello Apters, > > I noticed while making tests for an extension that supports older versions of PostgreSQL that the public keys for the 8.4 and 9.1 (but not 9.0) repos are out-of-date. Some details here: > > https://github.com/docker-library/postgres/issues/737 > > Any chance they could be updated? I realize that the community had dropped support for 9.4 and earlier, but as long as there are repos, perhaps the keys should be kept up-to-date? Hi, I left a comment in the github issue. Christoph ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-06-09 00:42 David E. Wheeler <[email protected]> parent: Christoph Berg <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-06-09 00:42 UTC (permalink / raw) To: Christoph Berg <[email protected]>; +Cc: pgsql-pkg-debian On Jun 8, 2020, at 10:28, Christoph Berg <[email protected]> wrote: > I left a comment in the github issue. Thanks Christoph! D Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-06-14 00:26 David E. Wheeler <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-06-14 00:26 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; +Cc: Christoph Berg <[email protected]>; pgsql-pkg-debian On Jun 8, 2020, at 20:42, David E. Wheeler <[email protected]> wrote: > On Jun 8, 2020, at 10:28, Christoph Berg <[email protected]> wrote: > >> I left a comment in the github issue. > > Thanks Christoph! Well that was unsatisfying. So I made a new Docker image, pgxn/pgxn-tools: https://github.com/pgxn/docker-pgxn-tools Works very well, except for Postgres 13 (and presumably future pre-releases). Is there some incantation I could put into the Dockerfile to permanently configure it to ready from the prerelease repo, too? Sorry for the newb question, I’m only a superficial apt user. Thanks, David Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-06-14 15:28 Christoph Berg <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: Christoph Berg @ 2020-06-14 15:28 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; +Cc: pgsql-pkg-debian Re: David E. Wheeler > Works very well, except for Postgres 13 (and presumably future pre-releases). Is there some incantation I could put into the Dockerfile to permanently configure it to ready from the prerelease repo, too? Sorry for the newb question, I’m only a superficial apt user. PG13 requires an extra "13" added to the sources.list entry: https://wiki.postgresql.org/wiki/Apt/FAQ#I_want_to_try_the_beta_version_of_the_next_PostgreSQL_relea... There's a shell script to automate these bits in postgresql-common 204 or newer: /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh -v 13 https://salsa.debian.org/postgresql/postgresql-common/-/blob/master/pgdg/apt.postgresql.org.sh (Unfortunately, buster has only version 200, so you'd need to install postgresql-common from buster-pgdg first, but if you do that, you have a trust path from buster via buster-pgdg to PG13 without fetching random things via wget.) Christoph ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-06-14 20:06 David E. Wheeler <[email protected]> parent: Christoph Berg <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-06-14 20:06 UTC (permalink / raw) To: Christoph Berg <[email protected]>; +Cc: pgsql-pkg-debian > There's a shell script to automate these bits in postgresql-common 204 > or newer: > > /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh -v 13 > > https://salsa.debian.org/postgresql/postgresql-common/-/blob/master/pgdg/apt.postgresql.org.sh Okay. I’m doing this: ADD https://www.postgresql.org/media/keys/ACCC4CF8.asc . RUN apt-key add ACCC4CF8.asc \ && rm ACCC4CF8.asc \ && echo deb http://apt.postgresql.org/pub/repos/apt buster-pgdg main > /etc/apt/sources.list.d/pgdg.list This is so that the container can install any supported version (except 13). Is it possible to have both? Should I grab apt.postgresql.org.sh and use it to set up both the normal repo *and* for 13? Something like: ADD https://salsa.debian.org/postgresql/postgresql-common/-/blob/master/pgdg/apt.postgresql.org.sh \ && apt.postgresql.org.sh \ && /apt.postgresql.org.sh -v 13 And then would it support `apt-get install postgresql-13`? Thanks, David Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-06-14 21:54 David E. Wheeler <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-06-14 21:54 UTC (permalink / raw) To: Christoph Berg <[email protected]>; +Cc: pgsql-pkg-debian On Jun 14, 2020, at 16:06, David E. Wheeler <[email protected]> wrote: > ADD https://salsa.debian.org/postgresql/postgresql-common/-/blob/master/pgdg/apt.postgresql.org.sh \ > && apt.postgresql.org.sh \ > && /apt.postgresql.org.sh -v 13 > > And then would it support `apt-get install postgresql-13`? Okay, I changed it to: ``` ADD https://salsa.debian.org/postgresql/postgresql-common/-/raw/master/pgdg/apt.postgresql.org.sh /usr/local/bin/ RUN chmod +x /usr/local/bin/apt.postgresql.org.sh \ && apt-get update \ && apt-get install -y --no-install-recommends build-essential pgxnclient ca-certificates gnupg2 \ && apt-get clean ``` And then I added code to my start script to call apt.postgresql.org.sh -p -v $PGVERSION However, when I try to install 13, I get: ``` Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: postgresql-13 : Depends: postgresql-client-13 but it is not going to be installed postgresql-server-dev-13 : Depends: libpq-dev (>= 13~~) but 11.7-0+deb10u1 is to be installed Depends: postgresql-client-13 but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` Is there something else that needs doing? Thanks, David Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-11 22:46 David E. Wheeler <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-10-11 22:46 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; +Cc: Christoph Berg <[email protected]>; pgsql-pkg-debian On Jun 14, 2020, at 17:54, David E. Wheeler <[email protected]> wrote: > Okay, I changed it to: > > ``` > ADD https://salsa.debian.org/postgresql/postgresql-common/-/raw/master/pgdg/apt.postgresql.org.sh /usr/local/bin/ > RUN chmod +x /usr/local/bin/apt.postgresql.org.sh \ > && apt-get update \ > && apt-get install -y --no-install-recommends build-essential pgxnclient ca-certificates gnupg2 \ > && apt-get clean > ``` > > And then I added code to my start script to call > > apt.postgresql.org.sh -p -v $PGVERSION > > However, when I try to install 13, I get: > > ``` > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > postgresql-13 : Depends: postgresql-client-13 but it is not going to be installed > postgresql-server-dev-13 : Depends: libpq-dev (>= 13~~) but 11.7-0+deb10u1 is to be installed > Depends: postgresql-client-13 but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > ``` > > Is there something else that needs doing? 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 Thanks, David Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-12 21:28 Christoph Berg <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: Christoph Berg @ 2020-10-12 21:28 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; +Cc: pgsql-pkg-debian 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 ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-13 14:31 Aaron Pavely <[email protected]> parent: Christoph Berg <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: Aaron Pavely @ 2020-10-13 14:31 UTC (permalink / raw) To: Christoph Berg <[email protected]>; David E. Wheeler <[email protected]>; pgsql-pkg-debian On Mon, Oct 12, 2020 at 4:28 PM Christoph Berg <[email protected]> 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-8... 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 ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-13 15:15 Christoph Berg <[email protected]> parent: Aaron Pavely <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: Christoph Berg @ 2020-10-13 15:15 UTC (permalink / raw) To: Aaron Pavely <[email protected]>; +Cc: David E. Wheeler <[email protected]>; pgsql-pkg-debian Re: Aaron Pavely > I think the issue (in part) is here: > https://salsa.debian.org/postgresql/postgresql-common/-/blob/master/pgdg/apt.postgresql.org.sh#L77-8... Ouch, I knew hard-coding the version in there would backfire some day. Thanks, I just pushed fix. I still don't have a smart way to automate that, though :( Christoph ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-13 17:07 David E. Wheeler <[email protected]> parent: Christoph Berg <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-10-13 17:07 UTC (permalink / raw) To: Christoph Berg <[email protected]>; +Cc: Aaron Pavely <[email protected]>; pgsql-pkg-debian On Oct 13, 2020, at 11:15, Christoph Berg <[email protected]> wrote: > Thanks, I just pushed fix. > > I still don't have a smart way to automate that, though :( That fixes it, thanks. Now, if I wanted to test Postgres 14 (dev), what additional steps would I have to take? Thanks, David Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-13 18:44 Christoph Berg <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 2 replies; 18+ messages in thread From: Christoph Berg @ 2020-10-13 18:44 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; +Cc: Aaron Pavely <[email protected]>; pgsql-pkg-debian Re: David E. Wheeler > That fixes it, thanks. > > 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 The PG14 packages currently have a bug in the "alternatives" handling for the manpages which prevents installation. I'll try to fix that now. (Or revert the breaking change.) Christoph ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-16 15:10 Christoph Berg <[email protected]> parent: Christoph Berg <[email protected]> 1 sibling, 0 replies; 18+ messages in thread From: Christoph Berg @ 2020-10-16 15:10 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; Aaron Pavely <[email protected]>; pgsql-pkg-debian Re: To David E. Wheeler > sudo /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh -v 14 -i > > The PG14 packages currently have a bug in the "alternatives" handling > for the manpages which prevents installation. I'll try to fix that > now. (Or revert the breaking change.) Fwiw, the packages have been fixed now. Christoph ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-17 23:30 David E. Wheeler <[email protected]> parent: Christoph Berg <[email protected]> 1 sibling, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-10-17 23:30 UTC (permalink / raw) To: Christoph Berg <[email protected]>; +Cc: Aaron Pavely <[email protected]>; pgsql-pkg-debian On Oct 13, 2020, at 14:44, Christoph Berg <[email protected]> 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 Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-18 00:58 Aaron Pavely <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: Aaron Pavely @ 2020-10-18 00:58 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; +Cc: Christoph Berg <[email protected]>; pgsql-pkg-debian On Sat, Oct 17, 2020 at 6:30 PM David E. Wheeler <[email protected]> wrote: > On Oct 13, 2020, at 14:44, Christoph Berg <[email protected]> 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 ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-18 00:59 David E. Wheeler <[email protected]> parent: Aaron Pavely <[email protected]> 0 siblings, 1 reply; 18+ messages in thread From: David E. Wheeler @ 2020-10-18 00:59 UTC (permalink / raw) To: Aaron Pavely <[email protected]>; +Cc: Christoph Berg <[email protected]>; pgsql-pkg-debian On Oct 17, 2020, at 20:58, Aaron Pavely <[email protected]> wrote: > 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. Would that get me the server-dev package, too? Thanks, David Attachments: [application/pgp-signature] signature.asc (833B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Update Old Version Public Keys? @ 2020-10-18 01:14 Aaron Pavely <[email protected]> parent: David E. Wheeler <[email protected]> 0 siblings, 0 replies; 18+ messages in thread From: Aaron Pavely @ 2020-10-18 01:14 UTC (permalink / raw) To: David E. Wheeler <[email protected]>; +Cc: Christoph Berg <[email protected]>; pgsql-pkg-debian On Sat, Oct 17, 2020 at 8:00 PM David E. Wheeler <[email protected]> wrote: > > On Oct 17, 2020, at 20:58, Aaron Pavely <[email protected]> wrote: > > > 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. > > Would that get me the server-dev package, too? > > Thanks, > > David > Yes, because the repository component '14' is specified as part of the value for $COMPONENTS when the repository installation is done by the apt.postgresql.org.sh script, here: https://salsa.debian.org/postgresql/postgresql-common/-/blob/32702b6cd4c50b8da9484f5f0a189a6db3ef79a... If, instead, the `-i` option is used, the $PIN value assigned is used later by `apt-get`, here: https://salsa.debian.org/postgresql/postgresql-common/-/blob/32702b6cd4c50b8da9484f5f0a189a6db3ef79a... -- Aaron ^ permalink raw reply [nested|flat] 18+ messages in thread
end of thread, other threads:[~2020-10-18 01:14 UTC | newest] Thread overview: 18+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2020-06-07 16:47 Update Old Version Public Keys? David E. Wheeler <[email protected]> 2020-06-08 14:28 ` Christoph Berg <[email protected]> 2020-06-09 00:42 ` David E. Wheeler <[email protected]> 2020-06-14 00:26 ` David E. Wheeler <[email protected]> 2020-06-14 15:28 ` Christoph Berg <[email protected]> 2020-06-14 20:06 ` David E. Wheeler <[email protected]> 2020-06-14 21:54 ` David E. Wheeler <[email protected]> 2020-10-11 22:46 ` David E. Wheeler <[email protected]> 2020-10-12 21:28 ` Christoph Berg <[email protected]> 2020-10-13 14:31 ` Aaron Pavely <[email protected]> 2020-10-13 15:15 ` Christoph Berg <[email protected]> 2020-10-13 17:07 ` David E. Wheeler <[email protected]> 2020-10-13 18:44 ` Christoph Berg <[email protected]> 2020-10-16 15:10 ` Christoph Berg <[email protected]> 2020-10-17 23:30 ` David E. Wheeler <[email protected]> 2020-10-18 00:58 ` Aaron Pavely <[email protected]> 2020-10-18 00:59 ` David E. Wheeler <[email protected]> 2020-10-18 01:14 ` Aaron Pavely <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox