severity 242696 important thanks On Sat, 2004-06-05 at 19:33 -0700, Debian Bug Tracking System wrote: > > severity 242696 grave > Bug#242696: net-snmp: [m68k] FTBFS > Severity set to `grave'. > No... making *unrelated* software is release critical, and warrants a "critical" severity instead of "grave". grave is defined as: 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. none of which describe this bug. "important" is the appropriate severity (in fact, it could be argued that "normal" is the appropriate severity, but I personally like to keep libtool-caused FTBFS bugs at important until I've thoroughly checked them myself). Folks, please stop artificially inflating bug severities in an attempt to get them noticed and/or fixed quicker. Most good maintainers are likely to have far better an idea of a bug's true severity/urgency than anyone passing through the BTS. In fact, this bug looks to need reassigning back to net-snmp because that package isn't linking its shared libraries properly; but I haven't had time to investigate fully, so haven't done that yet. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
Attachment:
signature.asc
Description: This is a digitally signed message part