Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2356863 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, lbrabec
The votes have been last counted at 2025-04-07 18:02 UTC and the last processed comment was #comment-964620
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
FinalFE +1
bluez-5.81-1.fc42 was never stable, I don't think it needs an FE. In F42 stable we have5.80-1.fc42 which works fine according to the bug.
bluez-5.81-1.fc42
5.80-1.fc42
Or was there another reason to propose this, @adamwill ?
yeah, there is, per @pbrobinson "that being said I believe/suspect it actually fixes some BT audio issues on the bluez that was stable so it's probably suitable for a FE." I've asked him for more details on that.
Peter wrote "I believe it fixes some MPRIS (BT input controls like vol +/- etc) issues (see #2332989)". Honestly that seems pretty thin to me, I think it'd probably be fine for it to go as a post-release update. So I'm a weak:
FinalFE -1
Discussed during the 2025-04-07 blocker review meeting [1]:
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-04-07/f42-blocker-review.2025-04-07-16.01.log.html
AGREED RejectedFinalFE
The following votes have been closed:
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.