Hello,

On 13/05/2022 12:39, Lukas Puehringer wrote:
Hi,

I’m upstream maintainer and sponsored downstream maintainer of 
‘python-securesystemslib’ [1]. I have recently, with the help of DD Holger 
Levsen, uploaded a new version of the package to fix a minor test bug and thus 
prevent autoremoval [2].

Unfortunately, migration to Testing is blocked due to a failing auto-build [3] 
and the package remains marked for autoremoval, as are two dependent packages, 
which I also maintain.

I was unable to reproduce the failing build or track down the reason, and I 
have a strong feeling that it was caused by some hiccup on the build system. My 
findings are documented in [4].




My questions to the list:
How can I prevent autoremoval of python-securesystemslib and its dependents? 
Should I make a “dummy” patch release to trigger a new migration?

You need a giveback.
I have just given it.

Best ,
Jerome



Cheers,
Lukas


[1] https://tracker.debian.org/pkg/python-securesystemslib
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008349
[3] 
https://buildd.debian.org/status/fetch.php?pkg=python-securesystemslib&arch=all&ver=0.23.0-1&stamp=1650975203&raw=0
[4] https://github.com/secure-systems-lab/securesystemslib/issues/407


--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to