On Mon, 2016-07-18 at 19:41 +0200, Andreas Metzler wrote: > I have been wondering why hugin 2016.2.0~rc1+dfsg-2 (urgency=low) will > be considered for testing migration after only 5 days and I think I found > the reason. > > Testing has 2016.0.0+dfsg-1, which was followed by > [2016-07-16] 2016.2.0~rc1+dfsg-2 in unstable (low) > [2016-07-11] 2016.2.0~rc1+dfsg-1 in experimental (low) > [2016-06-04] 2016.2.0~beta1+dfsg-1 in experimental (medium) > > britney seems to have remembered that 2016.2.0~beta1+dfsg-1 had medium > urgency and chose to consider this urgency for sid->testing migration. > > I think that is a bug, especially as dch uses medium by default for > uploads to experimental.
(dch uses medium by default for uploads to /all/ suites.) It's a feature, specifically because the information that britney has about urgencies (via dak) is of the form: dm-writeboost 2.2.1-1 medium libapache-mod-auth-kerb 5.4-2.3 medium i.e. there's no mention of suite. I don't know whether anything other than britney uses the data; if not then I guess it would be a simple dak patch to add the suite data if desired. Regards, Adam
