Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=1940163 ** Information from BlockerBugs App:
Commented but haven't voted yet: pbrobinson
The votes have been last counted at 2021-03-17 23:06 UTC and the last processed comment was #comment-722007
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 do not love this, but here we are.
Oh, I was only proposing it for form, sorry. @pwhalen and @jforbes are pretty relaxed about it and we don't think it really needs to block. Apparently this is still a scenario that not many real-world aarch64 users are gonna run into. We can also document the workaround - just ensure the install includes plymouth. Based on their expert opinion, I am:
BetaBlocker -1
Betablocker -1
Blocker -1
I think we can document it for beta, very few people are likely to be affected.
AGREED RejectedBetaBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F34 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.