Your message dated Thu, 11 Feb 2021 20:44:06 +0100
with message-id <c3a8adb8-6778-5d85-8648-02b9378bea00@debian.org>
and subject line Re: Bug#982399: unblock: adequate/0.15.4
has caused the Debian Bug report #982399,
regarding unblock: adequate/0.15.4
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.)
--
982399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982399
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
---------- Forwarded message ----------
From: Andreas Beckmann <anbe@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Cc:
Bcc:
Date: Tue, 09 Feb 2021 18:51:57 +0100
Subject: unblock: adequate/0.15.4
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package adequate
QA-maintained adequate fell out of testing due to python2 usage.
That was fixed recently, but it is currently blocked from reentering by
autopkgtest regressions and the corresponding RC bug.
As adequate is actively being used by piuparts, I'd like to see it in
bullseye. I'll take a look at what is going wrong there, but it's now
too late for a fixed package to migrate to testing on its own. So maybe
you could unblock (and/or override-autopkgtest or whatever) the current
version and the fixed one should then be able to migrate on its own.
Some of the failures are related to merged /usr (the
bin-or-sbin-binary-requires-usr-lib-library test is probably moot
nowadays) and the shared library failures are probably related to
toolchain improvements.
unblock adequate/0.15.4
Thanks
Andreas
---------- Forwarded message ----------
From: Paul Gevers <elbrus@debian.org>
To: Andreas Beckmann <anbe@debian.org>, 982399-done@bugs.debian.org
Cc:
Bcc:
Date: Thu, 11 Feb 2021 20:44:06 +0100
Subject: Re: Bug#982399: unblock: adequate/0.15.4
Hi Andreas,
On 09-02-2021 18:51, Andreas Beckmann wrote:
> Please unblock package adequate
Done, but....
> QA-maintained adequate fell out of testing due to python2 usage.
> That was fixed recently, but it is currently blocked from reentering by
> autopkgtest regressions and the corresponding RC bug.
> As adequate is actively being used by piuparts, I'd like to see it in
> bullseye. I'll take a look at what is going wrong there, but it's now
> too late for a fixed package to migrate to testing on its own. So maybe
> you could unblock (and/or override-autopkgtest or whatever) the current
> version and the fixed one should then be able to migrate on its own.
We're doing this because it's part of the Debian QA infrastructure, but
we're unhappy that is was only resolved so late. piuparts is put on the
key packages list to avoid removal; do we understand correctly that
adequate is not a Depends of piuparts because it's only installed inside
the chroot (a Depends would have avoided the removal)?
Paul
PS: if you would have "just fixed" the autopkgtest and uploaded at the
time this bug was filed, it would have migrated without any intervention.
PS2: we'll leave the RC bug open, please fix the autopkgtest.