Your message dated Fri, 28 Feb 2020 17:58:08 -0500
with message-id <[email protected]>
and subject line Re: Bug#927703: knot: autopkgtest depends on python3-lmdb
which is not in buster
has caused the Debian Bug report #927703,
regarding knot: autopkgtest depends on python3-lmdb which is not in buster
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 [email protected]
immediately.)
--
927703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927703
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: knot
Version: 2.7.6-2
Severity: important
User: [email protected]
Usertags: fails-always
Dear maintainers,
I was looking into the failure of your package on the ci.debian.org
infrastructure when run in testing. One of your autopkgtests depends on
python3-lmdb, which isn't supported anymore in testing/buster. Could you
please have a look and fix your autopkgtest? If fixing the test itself
is too difficult for now, can you please add the skip-not-installable
restriction to the authoritative-server test, to enable proper
unstable-to-testing migration testing?
Thanks for considering. And please note that fixing this issue is
eligible for an unblock if this happens not too long from now.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/k/knot/2278660/log.gz
autopkgtest: WARNING: package knot is not installed though it should be
autopkgtest: WARNING: package knot-dnsutils is not installed though it
should be
autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt
install on test deps directly for further data about failing
dependencies in test logs
Reading package lists...
Building dependency tree...
Reading state information...
Package python3-lmdb is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'python3-lmdb' has no installation candidate
authoritative-server FAIL badpkg
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Control: tags 927703 + wontfix
On Sun 2019-07-21 11:35:40 +0200, Paul Gevers wrote:
> Control: tags -1 buster
>
> On Sun, 21 Apr 2019 16:38:58 +0200 Paul Gevers <[email protected]> wrote:
>> I was looking into the failure of your package on the ci.debian.org
>> infrastructure when run in testing. One of your autopkgtests depends on
>> python3-lmdb, which isn't supported anymore in testing/buster. Could you
>> please have a look and fix your autopkgtest? If fixing the test itself
>> is too difficult for now, can you please add the skip-not-installable
>> restriction to the authoritative-server test, to enable proper
>> unstable-to-testing migration testing?
>
> https://tracker.debian.org/news/1043194/py-lmdb-086-11-migrated-to-testing/
>
> The issue is resolved in testing, so only exhibits itself in buster. I
> can understand it when this bug is closed as wontfix in buster.
I'm closing this issue, because it is resolved in testing.
Thanks for keeping an eye on this, Paul!
--dkg
signature.asc
Description: PGP signature
--- End Message ---
