On Thu, 9 Nov 2006 00:34:55 +0100 [EMAIL PROTECTED] (Marco d'Itri) wrote: > On Nov 08, "A. Costa" <[EMAIL PROTECTED]> wrote: > > > Sending Debian bugs upstream is the maintainers job. Obviously we
> Not if I disagree with them. That's wild, I wrote exactly the same thought in the next sentence, but you needed to cut me off. Anyway, I absolutely agree you shouldn't send bugs upstream when you don't agree they're bugs. Bug reporters are often mistaken, and filtering out dubious bugs is an important part of the maintainer's job. Moreover, I've been mistaken before, and am grateful that on those occasions I only annoyed the Debian guy rather the wider world. > > 3. We will not hide problems > It's my call to decide if this is a problem or not, and I say no. > Stop reopening this bug. I have doubts about that interpretation of Debian policy, and would like to remind you of the 'wontfix' tag. Isn't the whole point to allow for a maintainer being uncertain, or just wrong, (that never happens!), and what if you were wrong? Or simply just allowing there to be a space to disagree. wontfix This bug won't be fixed. Possibly because this is a choice between two arbitrary ways of doing things and the maintainer and submitter prefer different ways of doing things, possibly because changing the behaviour will cause other, worse, problems for others, or possibly for other reasons. http://www.debian.org/Bugs/Developer#tags Nobody can make you send it upstream, or wants you to if you don't believe in it. Yet since we do "prefer different ways of doing things" in regards to the specificity of a certain error message, it seems the 'wontfix' tag is more _accurate_, as it publicly reveals dissent, while 'closed' is less so, because it hides disagreement. So, barring good reasons why 'closed' is better, I expect to reopen this bug yet again, after a few days cooling time, as per the above 'wontfix' tag policy. Stay frosty... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]