@Matthieu, @Dave, thanks for the comments and details. I'm not blocking work to land, the 20.10 SRU could be accepted now and I didn't revert in that serie. The SRU team tries to ensure the fix is in the new serie so it doesn't get forgotten/regress when next version is out but I think it's pretty clear we are going to sort out the review details, that's not a blocker and SRU team has been happy in the past to let things in with the understand than $newserie is being sorted out
> If upstream say "yes" to the patches, without further discussion: that's > great, but there'd presumably still be some delay before another version > makes its way down to us, so we'd be applying *some* patch to make it work in > the interim. Again I'm not asking for the patches to be reviewed or accepted upstream before they are uploaded to Ubuntu, I'm just asking for them to be sent upstream and the reference to the email/report/merge request to be added to the patches. It would probably have been less work to just do it rather than type a long explanation here on why we need to distro patch in any case (which I never disagreed with) Sorry again but we have been bitten too often in similar situation where people never upstreamed the work when they said they would because they got busy with other things, and we are the ones paying the maintainance cost later on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
