Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2045329 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill, coremodule
The votes have been last counted at 2022-10-17 19:28 UTC and the last processed comment was #comment-821712
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
For a smooth(er) upgrade:
FinalFE +1
Seems unlikely to break much and would be nice to have.
Is this FTI (fails to install) or only FTBFS (fails to build)?
We usually accept FTI as FE in order to ease upgrades during freeze and ensure the final frozen tree is as 'installable' as possible. We don't usually accept FTBFS as there is not much point to it; FTBFS is really a git repo problem, not a package repo problem.
AGREED RejectedFinalFE
Discussed during the 2022-10-17 blocker review meeting: [0]
The decision to classify this bug as a "RejectedFreezeException (Final)" was made as this is only a fails-to-build bug and the existing package installs fine, and nobody is saying the existing package is broken. There's no clear justification for an FE here.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-10-17/f37-blocker-review.2022-10-17-16.01.txt
The following votes have been closed:
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.