Urgency bug, or am I missing something?
I just uploaded a security fix to unstable, with high urgency. However, I got
On Wednesday 02 August 2006 12:02, you wrote:
> Warning: high (security) is not a valid urgency; it will be treated as low
> by testing.
> to pool/main/c/cheesetracker/cheesetracker_0.9.9-6.diff.gz
> to pool/main/c/cheesetracker/cheesetracker_0.9.9-6.dsc
> to pool/main/c/cheesetracker/cheesetracker_0.9.9-6_i386.deb
The changes looks right:
> Format: 1.7
> Date: Wed, 2 Aug 2006 10:31:35 -0600
> Source: cheesetracker
> Binary: cheesetracker
> Architecture: source i386
> Version: 0.9.9-6
> Distribution: unstable
> Urgency: high (security)
> Maintainer: Wesley J. Landaker <firstname.lastname@example.org>
> Changed-By: Wesley J. Landaker <email@example.com>
And the "Urgency" field matches Debian policy 5.6.17, where it explicitly
states: "It consists of a single keyword usually taking one of the values
low, medium or high (not case-sensitive) followed by an optional commentary
(separated by a space) which is usually in parentheses."
Is this a bug, or am I actually just missing something here?