Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2177722 Information from BlockerBugs App: <img alt="2177722" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2177722" />
Commented but haven't voted yet: coremodule, zbyszek
The votes have been last counted at 2023-03-14 15:31 UTC and the last processed comment was #comment-846698
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
Discussed during the 2023-03-13 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as it's hard to make any decision here without some details of any proposed fix. We will leave this until there's actually a necessary decision to make (i.e. a proposed fix during the freeze period).
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-03-13/f38-blocker-review.2023-03-13-16.00.txt
As the assigned owner of the bug, I ask for this not to be made a blocker or a FE. The bug is generally void of detail and unreproducible. If anything, the fix would likely need to be in dnf, and that is already being handled in https://bugzilla.redhat.com/show_bug.cgi?id=1907030.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.