On Mon, 12 Sep 2022, Andy Smith wrote:
On Mon, Sep 12, 2022 at 12:00:20PM +0000, Andy Smith wrote:
Obviously, no one desires for there to be bugs, so your question
doesn't really make sense. "Should bugs make it into Debian releases"?
Ah, sorry, I think I misunderstood - you are literally asking if the
presence of a severity "serious" bug in Grub should have prevented
the whole 11.5 point release happening?
I don't know. The only documentation I can find on the matter is
about full Debian releases and even that says the bugs would have to
be apmrked "release-critical" (RC) to block release, so not even
"critical" may have postponed things.
Interesting. I didn't find this bug report until after I'd already
tracked down the culprit package and was ready to file my own bug.
My gut feeling is that there's going to be quite a lot of
"serious"-level bugs in any point release and that no one works to
associate these with a recent upload and then prevent that going
into a new point release.
It still feels more useful to focus on how such problems can be
avoided in future. I don't think we can explore the release team
looking at every "serious" bug in every package otherwise they'd
never get a point release out.
Agreed. While I tend to try to file bugs at the lowest severity that can
be justified, I know that others go the other way. This is one I'd
probably have filed as Grave or even Critical. (I see it's now been
bumped to Grave)
It just felt wrong to me that this bug (and version bump of the
package) could go to stable without someone at least acknowleging the
bug. AFAICT there's no fundamental reason it needed to go out. If it was
that the reporter should have marked it grave or critical then fair
enough, just unfortunate that they didn't.
The same version also went to oldstable - where it turns out it works
fine - so I can see how it could be missed but this was a bug that I
feel would have, if necessary, justified delaying the 11.5 release and I
wonder what a bug reporter should do in a case like this.
Fortunately, from my PoV, it came with a kernel update and at the
weekend, so I rebooted and had time to investigate what was going on.
Otherwise I might have been blissfully unaware until a power-cut...
Unfortunately, on Saturday morning I'd removed pvshim=1 from the last of
my guests and restarted them (successfully) so I wasn't 100% sure it
wasn't something I'd done wrong.
Tim.
