Hello, On Mon, Sep 12, 2022 at 10:15:41AM -0400, Michael Stone wrote: > There are automated processes that stop package migration at > certain severity levels, but they can't guess that something that > was filed at a low level really should have been higher.
I think in this case the package was already present in testing and stable-proposed-updates before the bug was found. It was reported as "grave" and bounced between that and "serious". Also I am not sure if there are the same processes around this for packages going in to stable-proposed-updates. The migrations you speak of are from unstable to testing, and also with "RC" bugs in testing blocking a full release. But stable updates go straight to stable-proposed-updates and I don't know if anyone is watching bugs specific to that when cutting a point release. Anyway what I am saying is, I'm not sure there is any level of severity setting that would have made a difference in this case, only perhaps a lot of people experiencing the problem in time and shouting about it (or automated testing to catch it). Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
