[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#509732: marked as done (Debian Policy doesn't include directive for filing RC bugs against the Policy)

Your message dated Sat, 27 Dec 2008 17:53:34 -0800
with message-id <20081228015334.GF4782@volo.donarmstrong.com>
and subject line Re: Bug#509732: Kalle's message #68
has caused the Debian Bug report #509732,
regarding Debian Policy doesn't include directive for filing RC bugs against the Policy
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

509732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509732
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: important

The Debian Policy Manual doesn't feature the Debian Bug Tracking
System. This makes it impossible to report a bug with RC severity in
the Bug Tracking System that permits RC bugs to remain in Debian when
the report is closed incorrectly and nobody notices before it is
archived (please see bug #227941.) Since the problem is only specific
to that bug, it would suffice to raise severity of #227941 to serious.
The current description of severities contained in doc-base (in
bug-maint-info.txt) lists RC bugs as critical, grave and serious, but
nothing in the policy qualifies #227941 as serious (there's no
directive that makes it a policy violation) and the bug isn't grave or
critical according to that description.

I am filing this bug so that this is resolved. According to the
description in that file (bug-maint-info.txt) this bug isn't RC as well
despite it permits RC bugs to remain in Debian as explained above. A
solution would be to include a directive in the Debian Policy that
requires any RC problem be marked as serious.

Please, mark this bug as serious if it's not going to happen in short.

--- End Message ---
--- Begin Message ---
On Sat, 27 Dec 2008, José Luis González wrote:
> And can another developer file a serious bug if an error was found
> in the Manual? If so, please, let the description of Severe in the
> canonical location be updated.

If such a bug was possible, it would fall afoul of "makes unrelated
software on the system (or the whole system) break".
> My point was that if nobody able to set the severity to serious
> cared about it the error could remain and so the RC bugs it could
> have caused.

Anyone can set the severity to an RC level; only certain people can
make the final adjudication of severity.
> Yes, it is. I understand the description of serious only legitimates
> the mantainer to set this severity to the policy package when a bug
> about an error in the Manual that can lead to RC bugs is filed.

I'm not following you at all here. It sounds like you're concerned
about some kind of hypothetical bug in policy which could cause
breakage in other packages. If such a bug were to happen, and it were
filed against the debian-policy package, it will have its severity
properly set, as there are no less than 10 people who read this list
who are also policy maintainers and/or RMs and/or responsible for the

Regardless, I'd much rather restrict myself to the non-hypothetical
problems that we need to deal with in Debian, so I'll stop here.
Closing this report with this message.

Don Armstrong

This can't be happening to me. I've got tenure.
 -- James Hynes _Publish and Perish_

http://www.donarmstrong.com              http://rzlab.ucr.edu

--- End Message ---

Reply to: