Julien Cristau writes ("Bug#831699: release.debian.org: urgency is sticky
across dists - low urgency on sid upload ignored"):
> 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?
Often, an upload to experimental has quite severe bugs. I think the
`urgency=high' for 2.0-2 means `if you are running 2.0-1 you *really*
want this update'. I think the urgency information can be displayed
in advance of the update by apt, so you can see whether you want to be
bothered. It's also helpful as a very brief summary for humans.
I doubt that many people use `experimental; urgency=high' to mean
`fixes an RC bug present in sid'. That would be an unusual way to
carry on. In those cases it is easy enough to manually make sure that
the upload to sid says `unstable; urgency=high'.
Does that make sense ?
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
