MIME-Version: 1.0
References: 
 <CAHo4unZmXujaaV9npNmEMQw26jaCH7=+2+hUuJjNkCN3WnOo7A@mail.gmail.com>
 <ZoLWQ7txLAyyFKZ_@msg.df7cb.de>
In-Reply-To: <ZoLWQ7txLAyyFKZ_@msg.df7cb.de>
From: Greg Smith <greg.smith@crunchydata.com>
Date: Sat, 10 Aug 2024 16:46:24 -0400
Message-ID: 
 <CAHo4unb-7E9+1-+aXnhEHOd=guoHRO0YePbZgdYyfEU8FzJYBw@mail.gmail.com>
Subject: Re: PostGIS files for PG17-b2
To: Christoph Berg <myon@debian.org>, Greg Smith <greg.smith@crunchydata.com>,
	pgsql-pkg-debian@postgresql.org, Paul Ramsey <paul.ramsey@crunchydata.com>
Content-Type: multipart/alternative; boundary="000000000000188e49061f5a5b4f"
Archived-At: 
 <https://www.postgresql.org/message-id/CAHo4unb-7E9%2B1-%2BaXnhEHOd%3DguoHRO0YePbZgdYyfEU8FzJYBw%40mail.gmail.com>
Precedence: bulk

--000000000000188e49061f5a5b4f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 1, 2024 at 12:16=E2=80=AFPM Christoph Berg <myon@debian.org> wr=
ote:

> PostGIS doesn't work with 17 yet:
>
> https://pgdgbuild.dus.dg-i.net/job/postgis-binaries-beta/93/architecture=
=3Damd64,distribution=3Dsid/console
>

Since this hasn't moved yet as of beta3, I dug in.  PostGIS is focused on
getting PG17 well supported in their 3.5 release, currently in alpha
testing, and that's probably why this rough edge has lingered around 3.4
for so long.

On the error log there's a pair of basic compiler issues and then a few
regression tests are failing.  Paul Ramsey dug in for me and has fixed the
compiler problem:
https://github.com/postgis/postgis/commit/0a8072199200a8323b5ddcfdcb89ed01d=
bd5f6b1

We're not 100% sure that will fix all the regression issues, but all seems
solved in his local build.  He tells me it's not unusual for those
particular tests to require per-version tweaks if there's still something
off.  I gave up on trying to build everything myself to check when I
realized postgis_3.4.2+dfsg-1.pgdg+2.dsc doesn't even have PG17 listed yet.

If it takes a full release of the upstream 3.4 PostGIS branch to replace
the sid 3.4.2 that's not building, we can ask Paul R to lean on speeding up
the next point rel.  I can't tell if that's the easiest way to navigate
this through the Debian stable process, or if this is going to be a PGDG
source change no matter.  Baton passed to you!

--
Greg Smith  greg.smith@crunchydata.com
Director of Open Source Strategy

--000000000000188e49061f5a5b4f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jul 1, 2024 at 12:16=E2=80=AFPM C=
hristoph Berg &lt;<a href=3D"mailto:myon@debian.org">myon@debian.org</a>&gt=
; wrote:</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">PostGIS doesn&#39;t work with 17 yet:<br>
<a href=3D"https://pgdgbuild.dus.dg-i.net/job/postgis-binaries-beta/93/arch=
itecture=3Damd64,distribution=3Dsid/console" rel=3D"noreferrer" target=3D"_=
blank">https://pgdgbuild.dus.dg-i.net/job/postgis-binaries-beta/93/architec=
ture=3Damd64,distribution=3Dsid/console</a><br></blockquote><div><br></div>=
<div>Since this hasn&#39;t moved yet as of beta3, I dug in.=C2=A0 PostGIS i=
s focused on getting PG17 well supported in their 3.5=20
release, currently in alpha testing, and that&#39;s probably why this rough=
 edge has lingered around 3.4 for so long.<br><div><br></div></div><div>On =
the error log there&#39;s a pair of basic compiler issues and then a few re=
gression tests are failing.=C2=A0 Paul Ramsey dug in for me and has fixed t=
he compiler problem:<br></div><div><a href=3D"https://github.com/postgis/po=
stgis/commit/0a8072199200a8323b5ddcfdcb89ed01dbd5f6b1">https://github.com/p=
ostgis/postgis/commit/0a8072199200a8323b5ddcfdcb89ed01dbd5f6b1</a><br></div=
><div><br></div><div>We&#39;re not 100% sure that will fix all the regressi=
on issues, but all seems solved in his local build.=C2=A0 He tells me it=
9;s not unusual for those particular tests to require per-version tweaks if=
 there&#39;s still something off.=C2=A0 I gave up on trying to build everyt=
hing myself to check when I realized postgis_3.4.2+dfsg-1.pgdg+2.dsc doesn&=
#39;t even have PG17 listed yet.<br></div><div><br>If it takes a full relea=
se of the upstream 3.4 PostGIS branch to replace the sid 3.4.2 that&#39;s n=
ot building, we can ask Paul R to lean on speeding up the next point rel.=
=C2=A0 I can&#39;t tell if that&#39;s the easiest way to navigate this thro=
ugh the Debian stable process, or if this is going to be a PGDG source chan=
ge no matter.=C2=A0 Baton passed to you!<br><br></div><div>--<br></div><div=
><div><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Greg Smit=
h=C2=A0 <a href=3D"mailto:greg.smith@crunchydata.com" target=3D"_blank">gre=
g.smith@crunchydata.com</a><br>Director of Open Source Strategy<br></div></=
div></div>=C2=A0</div></div></div>

--000000000000188e49061f5a5b4f--