Adam D. Barratt writes ("Bug#831699: release.debian.org: urgency is sticky
across dists - low urgency on sid upload ignored"):
> On 2018-06-20 15:55, Ian Jackson wrote:
> > What I don't understand is why it is not correct for britney to use
> > the urgency of the actual version it is considering migrating, rather
> > than some other version.
>
> If you upload 1.0-2 containing an RC bug fix, so with "Urgency: high"
> and then, before 1.0-2 has migrated, upload 1.0-3 with default urgency,
> what should happen?
Oh, I see. Sorry, I was being dim.
This seems to suggest that britney ought to do max of all the
urgencies of all the uploads to unstable after (or with higher
version than) the version in testing. Which requires the info from
dak discussed earlier in this bug log.
But I think it *also* requires the change to dpkg-genchanges, because
otherwise the urgency of uploads to unstable can be artificially
inflated there too.
I guess it is too much to hope that britney has access to the
changelog ? If it did it could do its own calculation, which would be
max of the changelog entries *mentioning unstable* between the version
in testing and the version being considered.
Regards,
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.
