Bug#484359: marked as done ([frontend/lintian] Urgencies are case-sensitive)
Your message dated Mon, 23 Jun 2008 10:15:22 -0700
with message-id <873an4ax91.fsf@windlord.stanford.edu>
and subject line Re: Bug#484511: Urgencies should all be lower case
has caused the Debian Bug report #484359,
regarding [frontend/lintian] Urgencies are case-sensitive
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
484359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484359
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 1.23.49
Hi,
During a discussion on #debian-release, it was confirmed that britney
treats urgencies as case-sensitive - i.e. high != HIGH. lintian's check
for valid urgencies, conversely, is case-insensitive.
The check should be modified to be case-sensitive. As "HIGH" is not a
valid urgency as far as britney is concerned, a package uploaded with
such an urgency will be treated as having the default urgency value,
which is currently "low".
Regards,
Adam
--- End Message ---
--- Begin Message ---
As noted below, dak was modified to support case-insensitive urgencies and
to lowercase them for britney.
Neil McGovern <maulkin@halon.org.uk> writes:
> On Sat, Jun 21, 2008 at 08:08:45PM +0100, Adam D. Barratt wrote:
>> On Sat, 2008-06-07 at 22:40 -0700, Russ Allbery wrote:
>> [...]
>>> With this patch applied, I think that these bugs are now moot, but I
>>> wanted to check before closing them. Is there any further work required
>>> in britney to treat urgencies as case-insensitive, or does the change in
>>> the log file written by dak solve that problem as well?
>> As I understand it, the change in dak means that the first time britney
>> is aware of the packages urgency it will already have been lower-cased.
>> Whilst britney still handles urgencies internally in a case-sensitive
>> manner, it should never be receiving an initial urgency for a package
>> which isn't in lower case.
> Agreed from my PoV.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
--- End Message ---
Reply to: