Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2136337 ** Information from BlockerBugs App:
Commented but haven't voted yet: bcotton
The votes have been last counted at 2022-10-20 18:49 UTC and the last processed comment was #comment-822233
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
From this page:
"although there is a release criterion that states 'All release-blocking images must boot in their supported configurations,' this criterion is not considered to be violated if a release blocking image fails to boot in some very particular hardware configuration but, in the general case, works fine. The intent of the criterion is that none of the release-blocking images must be so badly built or contain some bug of such showstopping severity that the image simply fails to boot in circumstances where it would usually be expected to work. The criterion is not intended to indicate that Fedora is somehow committed to ensuring its images boot on absolutely every system."
FinalBlocker -1
@catanzaro that's true, but this device is one that the ARM WG explicitly claims to support, which means we shouldn't apply that caveat.
I'm going to withhold my vote for the moment while we try to get more information about this. jforbes reports his hardware works as expected.
jforbes reports his hardware works as expected.
That's good enough for me. ;)
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.