Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2246800 Information from BlockerBugs App: <img alt="2246800" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2246800" />
Commented but haven't voted yet: adamwill, coremodule
The votes have been last counted at 2023-10-30 20:59 UTC and the last processed comment was #comment-881284
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
Doesn't this fix itself on launch day?
FinalFE -1
I am not sure if this has real impact. If someone is affected, they could still upgrade with --allowerasing for instance and then reinstall. kitty can be installed on F39.
--allowerasing
it's not a good idea to recommend using --allowerasing, as it's a blunt instrument: it will erase everything it needs in order to get the upgrade through. potentially if you're unfortunate enough to be affected by multiple issues like this, it will erase something you really didn't want it to.
AGREED AcceptedFinalFE
Discussed during the 2023-10-30 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedFreezeException (Final)" was made to prevent problems for early upgraders; it's not an important package so can't really break anything important.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-10-30/f39-blocker-review.2023-10-30-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.