Bug#621840: lintian: please warning when urgency in changes does not match the changelog
Niels Thykier <firstname.lastname@example.org> writes:
> Nope, I would keep the dpkg-genchanges behaviour to choose the highest,
> but ask the developer to be explicit about it. The good thing about the
> current behaviour is that if you import a bunch of changes from (e.g.)
> Ubuntu and one of them closes a security issue, then as long as you
> remember the -v option, then you get the right urgency.
> The idea was to make Lintian nag if there is a mismatch, mostly
> because if there is a security/priority issue, there is no problem in
> bumping the current changelog entry (to confirm it) and if there is not
> an issue, there is no reason for the urgency to be inflated (causing
> reduced time before testing migration).
Oh, okay, I see.
Hm. I guess I have no strong opinion. It feels weird to me to tag the
most recent upload as high urgency even if there's nothing in that change
to warrant high urgency just because earlier changes were high urgency,
but this may just be a personal twitch that I'd get over.
I don't know how frequently this might happen. It might be worth asking
the release team what they think.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>