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

[Julien Cristau <jcristau@debian.org>]

On Wed, Jun 20, 2018 at 15:55:31 +0100, Ian Jackson wrote:

> I experimented and dpkg-genchanges -vX provides a Changes file with
> the maximum urgency of any of the included changelog stanzas.  So if
> you say
> 
>    blah (2.0-3) unstable; urgency=low
>    blah (2.0-2) experimental; urgency=high
>    blah (2.0-1) experimental; urgency=medium
>    blah (1.0-1) unstable; urgency=whatever
> 
> and you (correctly) do your upload of 2.0-3 to unstable with -v1.0-1,
> the .changes file will say `high', even though from the pov of users
> of unstable and testing, it ought to be `low'.
> 
Why should it be low?  What else would the urgency=high in 2.0-2 mean?

Cheers,
Julien