Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oK2Uz-0003Ci-QL for pgsql-pkg-debian@arkaria.postgresql.org; Fri, 05 Aug 2022 18:56:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oK2Ux-0000dK-Nd for pgsql-pkg-debian@arkaria.postgresql.org; Fri, 05 Aug 2022 18:56:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oK2Uw-0000dB-S0 for pgsql-pkg-debian@lists.postgresql.org; Fri, 05 Aug 2022 18:56:39 +0000 Received: from mail-io1-xd32.google.com ([2607:f8b0:4864:20::d32]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oK2Ut-0003jO-Ke for pgsql-pkg-debian@postgresql.org; Fri, 05 Aug 2022 18:56:37 +0000 Received: by mail-io1-xd32.google.com with SMTP id i84so2547797ioa.6 for ; Fri, 05 Aug 2022 11:56:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pavely.net; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=X37bP+zeUvPq5ZVRXIoJcLVGMqlv159TwxxcoZldUQQ=; b=R51e97cfZuOUl+QDo2IYWA3zL9UQgpw2ZGd4DQWCui9X+umTwa5C6aWSC9KjV+f6Xp Ky4koFkBfMCGLDMBMvGPT5UY5CHbipx8n3PM1BM39ZBaXDK+XZY0XKnKA+dQqjA4mGJm MF/pTSrT07vMk8vkab1GGOFRYfoOhKLb1eTyA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=X37bP+zeUvPq5ZVRXIoJcLVGMqlv159TwxxcoZldUQQ=; b=4J35N4uMag5yQYy7mRnqLCrGJHIRrf3+ORI3gtORECpq7aIGhAu6C4yBgKyiP9WBJD A14ZU8OnPaQdq6jQFfPd3YJ50sV2GcxCEPopkVp9CXKJ3auHVlD36WOm9+qnfS/Q1BQE t8sGFDeIrDarQPYzeHR0mkWA8Ja99qBjCn2vDZflHcoSoFSuMMwRCYqcMBu4aBe3tIst MfQivzxrNhYglzIHyyVMiPi88q5DfIHUPd7XHYGuqSCXEC3KwQhPTFKoGmv3gkGM8Qsb 5gscH8h8XQyO0W4TcD3m2XrkD7dj4RqioQM0B0dDc4iJqeqogKoZKvgZQzmHvGd1P0FA x7ng== X-Gm-Message-State: ACgBeo3Lhk1yMmq9dKTxHV3Ijg3vUnf55PkkGL0TajwNKGJs27ijXrdf PAoizIXMvAGODk65TthzfsP98Y0ttXS6YuolHLxPdmMep34= X-Google-Smtp-Source: AA6agR4KEdcHMTlmlMFDPqg2jNgmHkq4dzCtlzVj+Yrg9oRK3xPZuL3XIsTyMPFbHv8h5a0VXjT5GePsF6oH/IUm/qM= X-Received: by 2002:a05:6602:3421:b0:684:57e7:509b with SMTP id n33-20020a056602342100b0068457e7509bmr516523ioz.98.1659725794519; Fri, 05 Aug 2022 11:56:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aaron Pavely Date: Fri, 5 Aug 2022 13:56:23 -0500 Message-ID: Subject: Re: Bullseye 10 and 11 servers packages To: Laurent Arnoud Cc: pgsql-pkg-debian@postgresql.org Content-Type: multipart/alternative; boundary="00000000000068469405e5830632" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000068469405e5830632 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Aug 5, 2022 at 1:29 PM Laurent Arnoud wrote: > Hi, > > I'm working at platform.sh and we are using your Debian packages for all = versions. We are trying to update to bullseye, but currently the 10 and 11 = servers are missing from this repository. I can see that there are builds s= uccessfully on your jenkins [10](https://pgdgbuild.dus.dg-i.net/job/postgre= sql-10-binaries/architecture=3Damd64,distribution=3Dbullseye/lastSuccessful= Build/artifact/) [11](https://pgdgbuild.dus.dg-i.net/job/postgresql-11-bina= ries/architecture=3Damd64,distribution=3Dbullseye/lastSuccessfulBuild/artif= act/) > > Are these debs not intended to be included in the public repos, or can we= find them published elsewhere? > > Thanks, > Laurent > > Are you using the 'main' component in your 'sources.list', or are you selecting specifically '10' and/or '11'? Correct: deb http://apt.postgresql.org/pub/repos/apt *bullseye*-pgdg main Incorrect: deb http://apt.postgresql.org/pub/repos/apt *bullseye*-pgdg 10 deb http://apt.postgresql.org/pub/repos/apt *bullseye*-pgdg 11 The incorrect form is valid if you wish to use the libpq from a prior major release, as detailed here: https://wiki.postgresql.org/wiki/Apt/FAQ#I_want_libpq5_for_version_X.2C_but= _there_is_only_version_Y_in_the_repository While I don't use bullseye, it's easy to check if the package is referenced in the repository (note the 'main' in the path): $ curl -s https://apt.postgresql.org/pub/repos/apt/dists/bullseye-pgdg/main/binary-am= d64/Packages | sed -n '/^Package: postgresql-10$/,/^$/p' | head -n 5 Package: postgresql-10 Version: 10.21-1.pgdg110+1 Architecture: amd64 Maintainer: Debian PostgreSQL Maintainers < team+postgresql@tracker.debian.org> Installed-Size: 23691 $ curl -s https://apt.postgresql.org/pub/repos/apt/dists/bullseye-pgdg/main/binary-am= d64/Packages | sed -n '/^Package: postgresql-11$/,/^$/p' | head -n 5 Package: postgresql-11 Version: 11.16-1.pgdg110+1 Architecture: amd64 Maintainer: Debian PostgreSQL Maintainers < team+postgresql@tracker.debian.org> Installed-Size: 45958 Regards, Aaron --00000000000068469405e5830632 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Aug 5, 2022 at 1:29 PM Laurent Ar= noud <la= urent.arnoud@platform.sh> wrote:
Hi,

I'm working at platform.sh and we are using your Debian packages for al=
l versions. We are trying to update to bullseye, but currently the 10 and 1=
1 servers are missing from this repository. I can see that there are builds=
 successfully on your jenkins [10](https://pg=
dgbuild.dus.dg-i.net/job/postgresql-10-binaries/architecture=3Damd64,distri=
bution=3Dbullseye/lastSuccessfulBuild/artifact/) [11](https://pgdgbuild.dus.dg-i.net/job/postgresql-11-binaries/arch=
itecture=3Damd64,distribution=3Dbullseye/lastSuccessfulBuild/artifact/)

Are these debs not intended to be included in the public repos, or can we f=
ind them published elsewhere?

Thanks,
Laurent

Are you using the '= main' component in your 'sources.list', or are you selecting sp= ecifically '10' and/or '11'?

Corre= ct:
deb = http://apt.postgresql.org/pub/repos/apt bullseye= -pgdg main=C2=A0

Incorrect:

The incorrec= t form is valid if you wish to use the libpq from a prior major release, as= detailed here:

While I don't use bullseye, it's easy = to check if the package is referenced in the repository (note the 'main= ' in the path):
$ curl -s https://apt.postgresql.org/pub/repos/apt/d= ists/bullseye-pgdg/main/binary-amd64/Packages | sed -n '/^Package: = postgresql-10$/,/^$/p' | head -n 5
Package: postgresql-10
Version: 10.21-1.pgdg110+1
Architecture:= amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@trac= ker.debian.org>
Installed-Size: 23691
$ curl -s https://apt.postgresql.org/pub/repos/apt/dists= /bullseye-pgdg/main/binary-amd64/Packages | sed -n '/^Package: post= gresql-11$/,/^$/p' | head -n 5
Package: postgresql-11
Version: 11= .16-1.pgdg110+1
Architecture: amd64
Maintainer: Debian PostgreSQL Mai= ntainers <team+postgresql@tracker.debian.org>
Installed-Size: 4= 5958

Regards,
Aaron
--00000000000068469405e5830632--