Discussion:
Why is knot migration blocked by done 1081191?
Add Reply
Jakub Ružička
2024-11-08 13:00:01 UTC
Reply
Permalink
Hello,

I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's
marked as Done but the bug still blocks knot migration for reasons I
don't understand:

https://qa.debian.org/excuses.php?package=knot

What do I need to do to finally finish migration?


Cheers,
Jakub Ruşička
Niels Thykier
2024-11-08 13:20:01 UTC
Reply
Permalink
Post by Jakub Ružička
Hello,
I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's
marked as Done but the bug still blocks knot migration for reasons I
https://qa.debian.org/excuses.php?package=knot
What do I need to do to finally finish migration?
Cheers,
Jakub Ruşička
Hi Jakub

The problem is that the BTS thinks that knot/3.3.9-1 is still in
unstable and is still affected[1]. As long as this is the case, the BTS
will inform Britney that knot is still affected by the bug in unstable.

This can occur if there are left other binaries that has not been
removed. Testing tends to "avoid" this trap because Britney is more
aggressive in its pruning left-over when it migrates to testing
(historically, Britney did not at allow out of binaries at all in
testing; now it allows it in some cases and prunes them out when possible).

As it is, "dak ls knot" does list knot/3.3.9-1 as a known version for
sid (rmadison should also show this as the case). It is unclear to me
why, but once you resolve that I think the rest should follow from there.

Best regards,
Niels

[1]:
https://bugs.debian.org/cgi-bin/version.cgi?package=knot-exporter;found=knot%2F3.4.0-2;found=knot%2F3.3.9-1;collapse=1;absolute=0;fixed=knot%2F3.4.0-3;fixed=knot-exporter%2F3.4.0-3;info=1
Chris Hofstaedtler
2024-11-08 13:30:02 UTC
Reply
Permalink
Post by Jakub Ružička
I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's
marked as Done but the bug still blocks knot migration for reasons I
https://qa.debian.org/excuses.php?package=knot
The problem is that the BTS thinks that knot/3.3.9-1 is still in unstable
and is still affected[1]. As long as this is the case, the BTS will inform
Britney that knot is still affected by the bug in unstable.
This can occur if there are left other binaries that has not been removed.
I imagine these bins are the leftovers:

knot-module-dnstap | 3.3.9-1 | unstable | armel
knot-module-dnstap-dbgsym | 3.3.9-1 | unstable-debug | armel
knot-module-geoip | 3.3.9-1 | unstable | armel
knot-module-geoip-dbgsym | 3.3.9-1 | unstable-debug | armel

and will need to be requested to be removed by filing an RM bug.

Chris

Loading...