Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2185827 ** Information from BlockerBugs App:
The votes have been last counted at 2023-04-11 18:22 UTC and the last processed comment was #comment-851124
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
FinalBlocker +1
While it does report the bug correctly, it appears that it doesn't. I agree it fails to satisfy https://fedoraproject.org/wiki/Basic_Release_Criteria#Failure_reporting
because "The installer must be able to report failures to Bugzilla, with appropriate information included."
FinalBlocker +1 because "The installer must be able to report failures to Bugzilla, with appropriate information included."
A voting command must be on a standalone line.
I mean, I hate to be a party pooper, but I'm kinda: FinalBlocker -1 on this. It does report the bug, which is the important thing. We get the information. It doesn't leave anything out (I checked). Yes, the user gets a concerning message, which sucks, but does this pass the last blocker smell test? Nah, not for me. But anyhow, I fixed it, and there's seven of you and one of me, so I guess: AGREED AcceptedFinalBlocker for now. if my fix blows up I may push harder for folks to reconsider.
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.