Re: Prevent autoremoval of python-securesystemslib and dependents
I'm not high up on the list of people at Debian, but I know for a fact that migration isn't instant. And neither is tracker.d.o updates. This is what I see listed for migration and update_excuses on the tracker for this package in Debian: excuses: Migration status for python-securesystemslib (0.22.0-1 to 0.23.0-1): Will attempt migration (Any information below is purely informational) Additional info: ∙ ∙ Updating python-securesystemslib will fix bugs in testing: #1008349 ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-securesystemslib.html ∙ ∙ 17 days old (needed 5 days) So I think this is just a "patience" game and we just need to wait for it to migrate (or attempt to migrate). Thomas On 5/13/22 10:02, Lukas Puehringer wrote: Hooray! Many thanks for the quick action, Jerome! The new build succeeded. Is there anything else needed to enter migration? Tracker still says that migration is blocked. Cheers, Lukas On 13.05.2022, at 14:02, Jerome BENOIT wrote: 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=all=0.23.0-1=1650975203=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
Re: Prevent autoremoval of python-securesystemslib and dependents
On 13/05/2022 15:02, Lukas Puehringer wrote: The new build succeeded. Is there anything else needed to enter migration? Tracker still says that migration is blocked. The Tracker usually takes a while to update. Check again tomorrow. Cheers, Peter
Re: Prevent autoremoval of python-securesystemslib and dependents
Hooray! Many thanks for the quick action, Jerome! The new build succeeded. Is there anything else needed to enter migration? Tracker still says that migration is blocked. Cheers, Lukas > On 13.05.2022, at 14:02, Jerome BENOIT wrote: > > 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=all=0.23.0-1=1650975203=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 >
Re: Prevent autoremoval of python-securesystemslib and dependents
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=all=0.23.0-1=1650975203=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 OpenPGP_signature Description: OpenPGP digital signature
Prevent autoremoval of python-securesystemslib and dependents
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? 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=all=0.23.0-1=1650975203=0 [4] https://github.com/secure-systems-lab/securesystemslib/issues/407
