I believe the segfault bug is bad enough for a release-critical grave classification as it results in data loss and limits usefulness of the package.
The current severity is important which is not enough to get the fixed version into stable. For new a package to be moved in to stable it needs to fix a release critical bug. Release critical bugs are critical, grave and serious. Is the segfaulting version "unusable or mostly so"? If this is the case then the severity should be set to grave. http://www.debian.org/Bugs/Developer#severities > 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://release.debian.org/lenny/rc_policy.txt > * causes serious data loss Loss of edit buffers or a single file may not be serious, but significant file system damage probably is. > * makes the package in question unusable or mostly so > * causes data loss Only usable if you don't close files. If you do you will loose your buffers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
