Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2242759 ** Information from BlockerBugs App:
Commented but haven't voted yet: lruzicka, saluki, coremodule, kparal, adamwill
The votes have been last counted at 2023-10-13 11:54 UTC and the last processed comment was #comment-878506
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
I tend to be
FinalBlocker +1
This issue sounds serious enough to block.
FInalBlocker +1
AGREED AcceptedFinalBlocker
Discussed during the 2023-10-09 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:
"For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed.", on affected RPi 4 systems. Note that the RPi4 is considered blocking hardware.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-10-09/f39-blocker-review.2023-10-09-16.00.txt
The following votes have been closed:
I believe we made an error marking this as a FinalBlocker instead of PreviousReleaseBlocker. @adamwill Am i right?
PreviousReleaseBlocker
oh, yes, probably.
REVOTE FinalBlocker AGREED AcceptedPreviousRelease
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.