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

Bug#582423: marked as done (tech-ctte: reaffirm that violating Debian Policy deserves RC bug)

Your message dated Tue, 22 Jun 2010 00:56:23 +0200
with message-id <20100621225623.GA5325@mails.so.argh.org>
and subject line RC bugs are decided by the release team
has caused the Debian Bug report #582423,
regarding tech-ctte: reaffirm that violating Debian Policy deserves RC bug
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

582423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582423
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: tech-ctte
Severity: normal

Please reaffirm that Debian bug #575786 against 'dpkg' package has
'serious' severity because of violation §7.6.2 of the Debian policy.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message ---

the current (long-standing) rule to decide about the RC-priority is
that the release team has the final say (apart from the obvious
exceptions to call the tech ctte or the developers at large). The
release team has documented in
http://release.debian.org/squeeze/rc_policy.txt when a bug should have
an RC priority and when not. Please refer to that document.

The maintainer has the first say whether a bug fits into that
description, but the release team could make the final decisions (and
they regularly do so; with the named exceptions per the constitution).

In case there are questions about the document, please contact the
release team. Only in case their decision isn't acceptable (which is
quite more than "you would have prefered a different decision", or
they refuse to do a decision), then contact the technical committee.

I'm closing this bug report now, as it looks like the release team
didn't review this decision. In case their is a need for the technical
committee to do a final decision, please open a new bug report,
stating the decision of the release team (or how you tried to get one,
and they failed to make one in an appropriate time frame) and why you
think their decision isn't acceptable for Debian.

Thanks for your support and your caring for Debian.


--- End Message ---

Reply to: