Bug#972255: transition: postgresql-common/221

[Christoph Berg <myon@debian.org>]

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi,

I think I have put everything in place that needs to be done to have
postgresql-common/221 migrate to testing, which makes the switch from
PostgreSQL 12 to 13 as the "supported" version concerning extension
module packages.

In the first round of extension I uploaded everything that was listed
as regression on the postgresql-common excuses page.

https://qa.debian.org/excuses.php?package=postgresql-common

Remaining issues listed there are:

autopkgtest for check-postgres/2.25.0-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass

-> The testsuite is flaky and the armhf problem hopefully goes away by
retrying (I already clicked the button). In any case, the regression
is test-only.

autopkgtest for gvmd/9.0.1-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)

-> Fixed in -4.1 in unstable

autopkgtest for osm2pgrouting/2.3.6-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)

-> I believe I fixed that in -2 in unstable, but debci is currently
still picking up the old postgis packages from unstable for the test.
In any case, the regression is test-only.

autopkgtest for omnidb/2.17.0+ds-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)
autopkgtest for pg-checksums/1.0-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)
autopkgtest for pgtap/1.1.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)

-> I added Breaks: for these in the last postgresql-common upload, the
issues are all fixed in unstable. (But the packages can only
transition along with postgresql-common.)

autopkgtest for postgresql-multicorn/1.4.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)

-> The only real problem, upstream has not yet released a fix for PG13
yet. Please remove postgresql-multicorn/1.4.0-2 from testing so we can
proceed.

(I have probably missed a few "not built on buildd" blockers on some of
the extension packages. Please schedule binnmus there, thanks.)

So, in summary: please
* remove postgresql-multicorn/1.4.0-2 from testing
* unblock postgresql-common/221

Thanks,
Christoph