Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2330681 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal
The votes have been last counted at 2025-02-24 18:51 UTC and the last processed comment was #comment-957645
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
as said in the ticket: "This issue only affected the debug kernel. A non-debug kernel works as intended." I think this is not a case of blocker, but maybe a FE?
BetaFE +1
Yeah, if this doesn't affect the regular kernel:
BetaBlocker -1
@kparal blockerbugs / blocker-review seems to have problems here. the bug appears twice in blockerbugs, and votes here don't appear to be applied to either of the entries there.
@adamwill Yeah, I still hope it's just cosmetic and it won't really break anything, so that I don't need to deal with it ASAP. But I'll try to figure it out. I created a ticket for it here: https://pagure.io/fedora-qa/blockerbugs/issue/286
well, if more folks vote -1 I can reject the bug as a blocker and we can see what happens :D
AGREED RejectedBetaBlocker
The following votes have been closed:
It would be nice if debug-kernel worked in Beta.
Discussed on 2025-02-24 in a blocker review meeting [1]:
!agreed 2330681 - AcceptedBetaFE - We would like to fix debug kernels ASAP, and we don't ship them on any medium, so this should be a safe freeze exception to grant.
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-02-24/f42-blocker-review.2025-02-24-17.01.log.html
AGREED AcceptedBetaFE
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F42 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.