Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2249392 ** Information from BlockerBugs App:
Commented but haven't voted yet: gui1ty, coremodule
The votes have been last counted at 2024-02-20 05:45 UTC and the last processed comment was #comment-896457
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
Probably the upgrade criterion fits best?
Anyway, feels pretty blockery in that you can hit it during a regular flow, and isn't easy to work around.
I just reopened the bug since I ran into trouble again. It's not exactly the same but it feels related. See info in bug.
I suppose some toddler holding a wand will get this ticket revived? Happy to open a new one if needed.
Discussed during the 2024-02-19 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as the reporter who reopened this issue may not have the same bug as the original reporter, the situation seems less clear-cut than it was for that reporter. We will delay the decision while attempting to get more information on Sandro's case, including testing on Fedora 40.
[0] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-02-19/f40-blocker-review.2024-02-19-17.00.log.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.