Hi, > > > I would like to get rid of the context switch a few days after the > > > original work, not the backporting work itself. > > > > TBH, I recommend you keep doing what you are doing. Perhaps already > > prepare the signed upload and upload it once it migrates. > > > > However, I can tell you that uploading to DELAYED works just fine also > > for backports, so you could do what you are suggesting (and I did it a > > few times), but considering the risk of the package effectively not > > migrating in time and by that possibly "breaking the rules" > > accidentally, I'd suggest not to do it. > > > > thanks. > that kind of makes sense. > > but... > > is the "version rule" not automated in some way (auto-rejecting packages > with the wrong version), but instead depends on the uploader's adherence to > the rules? > > if so, what's the reason? (philosophical reasons? lack of well-defined > version string for bpo with respect to the version in testing? lack of time > to implement it? no proper way to hook such an automatism into dak? ...) There are at least two reasons: a) nobody ever implemented it b) sometimes you want to allow exceptions, for example when there are critical bugs or security fixes Alex
Attachment:
signature.asc
Description: PGP signature