On Fri, Nov 14, 2003 at 08:32:37PM +0100, Adrian Bunk wrote: > On Fri, Nov 14, 2003 at 11:42:31AM -0600, Steve Langasek wrote: > > On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote: > > > Update: > > > From the look of it, jack-audio-connection-kit is waiting only for > > > * wine -- which has a grave bug that it doesn't work on 2.6.0, I > > > posted a workaround patch > > Why would this be considered grave? 2.6.0 hasn't even been officially > > released, has it? > Don't be ridiculous. > 2.6.0 will soon be released, and sarge already contains 2.6 kernel > images that are affected by this bug. grave makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. <http://www.debian.org/Bugs/Developer.html#severities> What criteria are you using to classify this as a grave bug, given that the vast majority of sarge users will be running 2.4 kernels? I don't recall seeing anything that made 2.6 support a "must" for sarge, so I don't see that an RC severity is justified here. -- Steve Langasek postmodern programmer
Attachment:
pgpJp4kLIUlLV.pgp
Description: PGP signature