Re: Bradford Boyle
> As a quick reference point, I spent a few minutes looking at how the
> PostgreSQL Yum Repository handles architectures and distributions. It
> looks like when a repo is EOLed, they stop providing updates to any
> package except PostgreSQL RPMs [1]. Additionally, it looks like RHEL 6
> was the last distribution to support x86.
Ack.
> Looking at the current release notes for Debian trixie [2], i686 will
> still be an officially supported architecture. I think the proposal to
> continue building the server, but disable building all extensions for
> 32-bit architectures is very reasonable.
I'd propose this plan:
* Remove buster-pgdg from apt.pg.o (buster-lts was EOLed last month)
* Remove i386 from sid-pgdg (packages are still preserved on
apt-archive.postgresql.org)
* Upload postgresql-17 to Debian unstable, with all architectures
supported [*] (once rc1 is there)
* When re-uploading all extensions to Debian to transition them from
16 to 17, disable extensions on 32-bit archs. Adding this should do
the trick:
Build-Depends: architecture-is-64-bit <!pkg.postgresql.32-bit>,
That way, people could still build extension packages manually if
they really wanted (dpkg-buildpackage -Ppkg.postgresql.32-bit).
* Remove postgresql-16 from unstable
Christoph
[*] On a side note, 32-bit powerpc did actually start to break:
https://buildd.debian.org/status/logs.php?pkg=postgresql-17&ver=17%7Ebeta2-1&arch=powerpc
I'll tell the package to ignore the regression test results there with
the next postgresql-common upload:
https://salsa.debian.org/postgresql/postgresql-common/-/commit/593fa32fa0c6d2a963a7b3b514d1d6a2423ef534
