Control: reopen -1 Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 [dak] Include suite information in UrgencyLog Control: block -1 by -2
On Tue, Jul 19, 2016 at 07:53:00PM +0000, Niels Thykier wrote: > Adam D. Barratt: > > On Tue, 2016-07-19 at 15:40 +0200, Goswin von Brederlow wrote: > >> On Mon, Jul 18, 2016 at 07:41:54PM +0200, Andreas Metzler wrote: > > [...] > >>> 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. > > [...] > >> Does it remember or does it parse the changelog and use the highest > >> priority since the version in testing? The hugin changelog contains > >> the urgency=medium entry so this seems a valid urgency to use. > > > > britney knows nothing about changelogs. The input is a strictly > > chronological (in terms of when dak accepted the package) list of source > > package name, version and urgency tuples for all uploads to the main > > archive. > > > > Regards, > > > > Adam > > > > For the people interested, the input data is available from [1]. If you > want it changed, it will need to be fixed in dak (producer) and Britney > (as the consumer). I think that's the proper fix for this and I would prefer to avoid adding even more special-casing code to dch. > From my PoV: Patches welcome and will gladly help people, who are > interested in it. I don't expect to have time to fix it myself any time > soon - but as I said; I will gladly help people getting started. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
signature.asc
Description: PGP signature
