Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2175244 Information from BlockerBugs App: <img alt="2175244" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2175244" />
Commented but haven't voted yet: adamwill, coremodule
The votes have been last counted at 2023-03-06 20:00 UTC and the last processed comment was #comment-845121
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
BetaBlocker -1
As this apparently only happens on the Minimal image, which is not blocking.
Oh, huh. That's true. I kinda thought it was/should be...
Not a blocking deliverable, but would still like to see it fixed.
BetaBlocker -1 BetaFE +1
AGREED RejectedBetaBlocker Minimal image is not a blocking deliverable.
The following votes have been closed:
AGREED AcceptedBetaFE
Discussed during the 2023-03-06 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedFreezeException (Beta)" was made as this makes the image unusable for interactive installs, it's certainly serious enough to grant a freeze exception.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-03-06/f38-blocker-review.2023-03-06-17.00.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.