Control: severity -1 grave Control: fixed -1 0.35 Control: tags -1 -unreproducible
On 2015-12-04 14:36:01, Jameson Graef Rollins wrote: > On Fri, Dec 04 2015, Antoine Beaupré <anar...@debian.org> wrote: >> On 2015-12-04 12:50:47, Jameson Graef Rollins wrote: >>> I can build a jessie rescue image on my stretch/sid system no problem. >> >> I guess my parallel universe is irrelevant then. >> >> sigh... why did you change the severity? it's still a grave issue in >> jessie, and i can reproduce it there. did you try to reproduce it in >> jessie before marking it as unreproducible? > > I am not discounting your circumstances, Antoine, but I don't think the > package should be removed from testing because you can't build an image > under your particular circumstances. The package is known to be working > fine in testing, so the issue is clearly not release critical. See > https://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. > > Severities such as grave and critical should be reserved for extenuating > circumstances only, which do not apply in this case. Again: while the package works in stretch and sid, it doesn't work in jessie. I am not saying the package should be removed from testing, but then this should be marked as "grave" nevertheless, which will *not* make it removed from testing, if a "fixed" version is present there. *not* marking this as grave will make it difficult to have a stable update to fix this bug. Also, the package is "unusable or mostly so", which seems to be a sufficient condition for making the bug as grave, according to the very description you are quoting. I am therefore reverting part of your changes to mark the bug as "reproducible, grave and found in jessie". I do not think this will make it drop from testing. A. -- You Are What You Is - Frank Zappa
