Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2402498 ** Information from BlockerBugs App:
Commented but haven't voted yet: lruzicka
The votes have been last counted at 2025-10-20 18:58 UTC and the last processed comment was #comment-990184
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
FinalFE +1
at least. Not sure on specific blocker criteria.
Yeah, I'm not totally sure about blocker as it seems like this so far only affects one fairly niche device and rpi4 in a non-standard config, but at least:
especially if we're no-go this week (which seems very likely).
That makes sense Adam.
AGREED AcceptedFinalFE
The following votes have been closed:
Discussed at the blocker review meeting on 20th Oct. 2025
AGREED AcceptedFinalBlocker
This is accepted as a blocker on the basis that it's believed to affect relatively common configurations of the Raspberry PI 4 (a very commonly used device for Fedora aarch64) as well as the reported Nanopi R5C (@adamwill:fedora.im, 17:52:59)
https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-10-20/f43-blocker-review.2025-10-20-16.02.html
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F43 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.