Re: Sebastian Ramacher
> > autopkgtest for omnidb/2.17.0+ds-2: amd64: Regression ♻ (reference ♻),
> > arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386:
> > Regression ♻ (reference ♻)
>
> The autopkgtests for omnidb 2.17.0+ds-4 also fails:
>
Re: Sebastian Ramacher
> Removal hint added. Could you please file an RC bug against
> postgresql-multicorn so that once removed from testing britney doesn't
> try to migrate?
Thanks.
Bug: #972285
Christoph
On 2020-10-15 12:34:43 +0200, Christoph Berg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@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,
Hi Christoph
On 2020-10-15 12:34:43 +0200, Christoph Berg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Hi,
>
> I think I have put everything in place that needs to be done to have
> postgresql-common/221
Re: Christian Marillat
> Bug #971586 against postgresql-debversion is not fixed (missing a
> package for postgresql 13).
That is not related to the first step of the transition. The remaining
modules will follow once the first step is through.
Christoph
On 15 oct. 2020 12:34, Christoph Berg wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@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
Package: release.debian.org
Severity: normal
User: release.debian@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"
7 matches
Mail list logo
