On Sat, 10 Feb 2018 at 23:17:34 +0100, Cyril Brulebois wrote: > Guilhem Moulin <guil...@debian.org> (2018-02-10): >> Should we? I was refraining from uploading 2.2.1 due to the following >> note in the transition page >> >> “Please avoid uploads unrelated to this transition, they would >> likely delay it and require supplementary work from the release >> managers.” — https://tracker.debian.org/pkg/cryptsetup > > This is mainly targeted at packages which are included in the reverse > dependencies graph: if they in turn get uploaded frequently, that tends > to lengthen delays for the actual migration of all related packages. > More on that in my last paragraph. > […] > cryptsetup-bin is a binary package built from the cryptsetup source > package, so its RC bug count is included in cryptsetup's RC bug count, > and having an extra bug compared to what's in testing means it's a > regression = a blocker for the migration.
I see, thanks for the poke and the explanation. > Back to the question at end: of course, fixing a regression in your > package is something you want, and actually need to do. It's totally > related to getting your package in shape, so please follow Michael's > advice on this. Uploading right after hitting save :-) -- Guilhem.
signature.asc
Description: PGP signature
