[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#972255: marked as done (transition: postgresql-common/221)

Your message dated Sun, 18 Oct 2020 12:35:40 +0200
with message-id <20201018103540.GE2232609@ramacher.at>
and subject line Re: Bug#972255: transition: postgresql-common/221
has caused the Debian Bug report #972255,
regarding transition: postgresql-common/221
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
972255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972255
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
On 2020-10-15 12:34:43 +0200, Christoph Berg wrote:
> 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

postgresql-common | 221           | testing      | source, all

Cheers

> 
> Thanks,
> Christoph
> 

-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: