On Tue, Sep 1, 2009 at 18:25:20 +0200, Moritz Muehlenhoff wrote: > The problem is that the standard severities cannot be mapped 1:1 on > the kernel package. Since the kernel is the core component of 99% > of all Debian systems, it's in the nature of the beast that any > problem which makes a system unbootable renders the package unusable > for the person filing the bug and the default descriptions lead bug > reporters to believe that grave or above is the correct severity. >
A solution might be for the kernel packages to include the below information in a 'presubj' file to be shown by reportbug? > As far as the kernel is concerned, the severies applied by current > practice are more or less: > > critical: > - bugs leading to data loss on a wide range of systems > > grave: > - security bugs leading to remote denial of service or local privilege > escalation > - bugs which make the package unusable on a wide range of systems > > serious: > - a severe violation of Debian policy (as in the standard severities) > > important: > - bugs which render some systems (e.g. a certain model or systems > with a specific adaptor/device) unusable > > normal to wishlist are treated as in standard policies. > > Since this is a common mistake, it might be a good idea to display > different descriptions when filing a bug against the linux-2.6 > source package. This is what Maks's bug report is about. > Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
