在 2020-01-08三的 16:36 +0530，Pirate Praveen写道： > > On വ്യാ, Jan 2, 2020 at 21:43, debacle <debacle@debian.org> > wrote: > > On 2020-01-02 11:53, Lisandro Damián Nicanor Pérez Meyer wrote: > > > El jue., 2 ene. 2020 08:28, Julien Cristau <jcristau@debian.org> > > > escribió: > > > > No, it'll eventually get retried and (assuming it passes) the > > > migration > > > > block will lift. > > > > > > And "eventually" is normally how many days? > > > > If I've learned one thing in Debian, it's patience! > > Its already 10 days [1] and newly uploaded packages are now getting > migrated. So I don't think the packages failed due to bug are getting > any priority over the newly uploaded ones. I'd have expected them to be > retried before new packages. Can this still be done? > > [1] https://tracker.debian.org/pkg/micro I checked the piuparts documentation just then [2] and found out that unlike ci.d.o or reproducible-build checks, the piuparts test will *not* automatically be retried for the same package of the same version (same upload). If I understand correctly, it seems that those packages uploaded in the period when the piuparts were broken will never migrate to Testing unless another upload is made. This is definitely far from ideal. Is it possible to manually trigger a retry for each packages hit by this regression? At least asking maintainers to search throught britney update excuses [3] and making another upload is really not a valid option. BTW, searching "Rejected due to piuparts regression" in [3] gives 135 results. [2] https://wiki.debian.org/piuparts/FAQ#Q._Can_I_somehow_tell_piuparts_to_retest_my_package.3F [3] https://release.debian.org/britney/update_excuses.html -- Thanks, Boyuan Yang
Attachment:
signature.asc
Description: This is a digitally signed message part