On 2006-10-02 02:03:56 -0700, Debian Bug Tracking System wrote: > > That's the problem. Some bugs appear only with some configuration or > > with some (non-x86) architecture, and for this reason, maintainers > > will downgrade the bug severity to important or normal, even though > > the bug has nasty effects, such as a broken package system (i.e. no > > possible going back or fixing with "apt-get install -f") or data > > loss. In the case of bug 237509, it was because the bug didn't > > "affect people upgrading from woody". > > *shrug*; that's the nature of the beast. There's no way to sanely > apply global tags to describe exactly in what circumstances bugs take > effect.
This is not what I was asking. I'm just asking for a tag (or anything that would provide a similar feature) that indicates that the package may break the system -- in any circumstance; then the user could look at the bug and see if he is concerned or not. > > This is a technical problem, as the severities can't express what > > the problem is exactly (or what the consequences are), making them > > incomplete. > > It's an insolvable problem, not just a technical one. It's not insolvable; it's very similar to severities. > Regardless, before reopening this bug, if you think additional > severities or tags are in order, you need to follow the instructions > in #144633 et al. and use usertags in order to implement it. They mention "usertags", but I can't find anything about that on http://www.fr.debian.org/Bugs/Developer and other web pages. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
