Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2243872 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill
The votes have been last counted at 2024-02-12 17:28 UTC and the last processed comment was #comment-895213
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
I feel like this violates the upgrade requirements criteria, as mentioned in the ticket the workaround (--exclude sdubby) likely won't happen when updating via say, gnome-software.
--exclude sdubby
(that is, if sdubby is in any of the blocking package sets by default, which I am not sure right now)
AGREED AcceptedBetaBlocker
The following votes have been closed:
@frantisekz the problem is/was that it is/was in the @anaconda-tools comps group, and dnf pulls in new packages in that group on upgrade. it should be resolved now by being marked 'optional', I hope, but it needs testing.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.