-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-04-10 04:24, Russ Allbery wrote:
Niels Thykier ni...@thykier.net 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
Niels Thykier ni...@thykier.net writes:
Alternatively we could look for urgency/priority in the changelog
entry (similar to the upload to unstable check we currently do), if
you feel that is less weird.
Well, but similar to the urgency setting itself, one would naturally put
that in the
Package: lintian
Version: 2.5.0~rc2
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
Looking at two uploads today ([1], [2]) I noticed that the urgency
of the newest entry of the changelog was low, but the changes had
urgency high or critical. The high/critical urgency was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-04-09 19:20, Russ Allbery wrote:
Niels Thykier ni...@thykier.net writes:
Looking at two uploads today ([1], [2]) I noticed that the urgency of
the newest entry of the changelog was low, but the changes had urgency
high or critical.
Niels Thykier ni...@thykier.net writes:
Looking at two uploads today ([1], [2]) I noticed that the urgency of
the newest entry of the changelog was low, but the changes had urgency
high or critical. The high/critical urgency was most likely inherited
from earlier entries.
If the package is
Niels Thykier ni...@thykier.net 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
6 matches
Mail list logo
