Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored after previous experimental medium-urgency upload

[James McCoy]

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 +, 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

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored after previous experimental medium-urgency upload

[Niels Thykier]

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).
  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.

Thanks,
~Niels

[1] https://ftp-master.debian.org/britney/urgencies/

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored after previous experimental medium-urgency upload

[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

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored after previous experimental medium-urgency upload

[Andreas Metzler]

On 2016-07-19 Julien Cristau  wrote:
> On Mon, Jul 18, 2016 at 18:51:33 +0100, Adam D. Barratt wrote:

> > On Mon, 2016-07-18 at 19:41 +0200, Andreas Metzler wrote:
[...] 
>>> 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.
[...] 
> Closing as not a bug.

Hello,

Ok, I will accept this, seems there is a judgement call involved.

It seemed crystal clear to me that testing propagation using the
priority of uploads to experimental was a bug. Simply because uploads to
experimental *never* are subject to testing propagation, testing
propagation checking only starts with the sid upload.

I will try to get dch changed to use low priority for experimental
uploads.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored after previous experimental medium-urgency upload

[Goswin von Brederlow]

On Mon, Jul 18, 2016 at 07:41:54PM +0200, Andreas Metzler wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: britney
> 
> Hello,
> 
> 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.
> 
> cu Andreas

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.

MfG
Goswin

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored after previous experimental medium-urgency upload

[Julien Cristau]

On Mon, Jul 18, 2016 at 18:51:33 +0100, Adam D. Barratt wrote:

> 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.
> 
Closing as not a bug.

Cheers,
Julien

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored after previous experimental medium-urgency upload

[Adam D. Barratt]

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

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored after previous experimental medium-urgency upload

[Andreas Metzler]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: britney

Hello,

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.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'