Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2396015 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill, geraldosimiao
The votes have been last counted at 2025-09-20 04:19 UTC and the last processed comment was #comment-986588
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
FinalBlocker +1
Well, I don't think the proposed criterion works here - "The installed system must be able appropriately to install, remove, and update software with the default console tool for the relevant software type (e.g. default console package manager). This includes downloading of packages to be installed/updated." is a requirement for the package management tools to work appropriately. Broken packages are not in scope there.
We could argue this is a violation of "For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed", but...is it? Does upgrading from a stock F42 Workstation install currently fail due to this?
I agree with Adam, system upgrade is working fine, at least nobody else reported this error before and I see lot of people upgrading their systems to f43 beta in the last few days.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F43 is no longer tracked by BlockerBugs, closing this ticket.