Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2124986 Information from BlockerBugs App: <img alt="2124986" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2124986" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-09-13 05:03 UTC and the last processed comment was #comment-816437
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
BetaBlocker -1
I don't see that this violates any of the basic or beta criteria.
Agreed, unless I'm unaware of something, I don't think there are any Beta criteria-violating consequences to upowerd failing to start. It's inconvenient but I don't think it will cause systems to melt or anything, and it's probably OK for it to be fixed with an update.
FinalBlocker +1
Discussed during the 2022-09-12 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as the vote here is kind of split, but in any case the bug will be closed soon as it's confirmed fixed in 5.19.8, so we'll just punt it and it should have gone away by next week.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-09-12/f37-blocker-review.2022-09-12-16.01.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.