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 1oKy2q-00070T-Hc for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 08 Aug 2022 08:23:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oKy2o-00069s-0F for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 08 Aug 2022 08:23:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oKxmb-00013b-9C for pgsql-pkg-debian@lists.postgresql.org; Mon, 08 Aug 2022 08:06:41 +0000 Received: from mail-lf1-x12d.google.com ([2a00:1450:4864:20::12d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oKxmY-0003GL-Eg for pgsql-pkg-debian@postgresql.org; Mon, 08 Aug 2022 08:06:40 +0000 Received: by mail-lf1-x12d.google.com with SMTP id r17so11485551lfm.11 for ; Mon, 08 Aug 2022 01:06:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=platform.sh; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=ZgyC+hq7KZQLa1jf9UQ0cvD0uUMtuWycWtRyDDt2AcA=; b=OSNcaR7KYG3qcmmqxra8qEi3Gt3i3bRa135zKcE3HZF41IYvMWkuL4EcA+qzxd7AxG rsUEbuAiLlfMaOMUzfQItr1KDYRQTQnq38hAB213k+C2fdYaOZkqdmsSB06B03rmCKm9 FZMxHiS3cDESYZkZ6P5uGTsKSHpapAD1u09Lmv6W6YVI0UrhIF8gL03muXkC8z8jCDR5 ChOpaRDgAz/rlNdHcjIfTe4blDSNQPG+Cn1n+yQss4KAR6J8yaco5fxs71ReimwZG9eT v30mHEAN7I6IZ9GIhz6mWobHT2oCtNtg8+s1pb1EZ1thN5QTh6OnjAACW0DeuREPhcvL Td0Q== 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=ZgyC+hq7KZQLa1jf9UQ0cvD0uUMtuWycWtRyDDt2AcA=; b=rdPfcFRp7DBMcr476t0EBFgPnxOXAWYhuZwbJ9cMXutOC3Orp8Qfe2vAbZQ7ZTaJ0Y 8LK4XO2+32PJlTZFmWxVNBwUxB08NUydVvBgMZuKfJrkTx0UUhi2wbDAAeODckUodN8H tz8Odh1RL7Inbc5B2afCHg0+46oF4cOdp8y7Ighew+91zoF7LBmcm7swncczDtJNwHNy 288+VzUP7lwgl5HfBUL+O4XEdLeIeOt/ZU5JBvXz+VQ1q323/CmLUYs0VTcYig09W2qZ aSztw/F3K4l+oIxt405alhyJCONz1m1rIozbx8ol04HqNThHLTAnWOVOQ0qGRfPE3MWI SJcQ== X-Gm-Message-State: ACgBeo2aW6ZoVeZTxeh4ihZawPwPKhYBgnfVPeV3+xJnZRtee00hKycK iLmgUoZDAv72lpkGAfEZd7uOfzjiiBzi4vCPPdIzQFFBgXDfhw== X-Google-Smtp-Source: AA6agR6Q5SQiK6j/s3qoTUEqA5kbSo/sppDnckLKx3D3K2iloA2MLxARErP47HNdRia7zQCfNiKh7Kao+pu/2Aqftpc= X-Received: by 2002:a05:6512:a87:b0:48b:a2ec:80b7 with SMTP id m7-20020a0565120a8700b0048ba2ec80b7mr2426815lfu.285.1659945996924; Mon, 08 Aug 2022 01:06:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Laurent Arnoud Date: Mon, 8 Aug 2022 10:06:55 +0200 Message-ID: Subject: Re: Bullseye 10 and 11 servers packages To: Aaron Pavely Cc: pgsql-pkg-debian@postgresql.org Content-Type: multipart/alternative; boundary="0000000000007e4f1605e5b64b5c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007e4f1605e5b64b5c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Aaron, Yes we are using main as source, but I think it failed because we are using postgis-2.5 for pg10 and 11 and I was wrongly checking on the browser 14 Packages list instead of main. Thanks for the quick reply. Cheers, Laurent On Fri, Aug 5, 2022 at 8:56 PM Aaron Pavely wrote: > 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 = successfully on your jenkins [10](https://pgdgbuild.dus.dg-i.net/job/postgr= esql-10-binaries/architecture=3Damd64,distribution=3Dbullseye/lastSuccessfu= lBuild/artifact/) [11](https://pgdgbuild.dus.dg-i.net/job/postgresql-11-bin= aries/architecture=3Damd64,distribution=3Dbullseye/lastSuccessfulBuild/arti= fact/) >> >> Are these debs not intended to be included in the public repos, or can w= e 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_b= ut_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-= 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@tracker.debian.org> > Installed-Size: 23691 > $ curl -s > https://apt.postgresql.org/pub/repos/apt/dists/bullseye-pgdg/main/binary-= amd64/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 > --0000000000007e4f1605e5b64b5c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Aaron,

Yes we are using m= ain as source, but I think it failed because we are using postgis-2.5 for pg10 and 11 and I was wrongly checking on the browser 14 Packages = list instead of main. Thanks for the quick reply.

= Cheers,
Laurent

On Fri, Aug 5, 2022 at 8:56 PM Aaron Pav= ely <aaron@pavely.net> wrote:=
On Fri, Aug 5, 2022 at 1:29 PM Laurent Arnoud <laurent.arnoud@pl= atform.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
--0000000000007e4f1605e5b64b5c--