Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2080938 Information from BlockerBugs App: <img alt="2080938" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2080938" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-05-02 18:32 UTC and the last processed comment was #comment-795439
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
The same bug, just for gzip, is in #777. Some justification is in https://pagure.io/fedora-qa/blocker-review/issue/777#comment-794014
FinalFE +1 FinalBlocker 0 (can be convinced)
Per https://bugzilla.redhat.com/show_bug.cgi?id=2080938#c2 FinalBlocker +1
FinalBlocker +1
FinalBlocker -1 FinalFE +1
This is for consistency with the gzip issue, which we did not take as a blocker. The criterion says "which cannot be satisfactorily resolved by a package update (e.g. issues during installation)" - this is not an issue that's likely to be encountered during installation or typical use of the live image, IMHO.
AGREED RejectedFinalBlocker AGREED AcceptedFinalFE
Discussed during the 2022-05-02 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made based off precedent set with the same bug in gzip (2073312) which was rejected as a blocker, this is rejected as it can be satisfactorily resolved with an update; the issue is not likely to be encountered during installation or typical use of a live image.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-05-02/f36-blocker-review.2022-05-02-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.