Comment 21 for bug 2047780

I appreciate everyone is frustrated. BlueZ isn't really staffed, it's just something I look at once or twice a year. The diff to Debian is shrinking over the long term, but again that's something I don't look at very often.

The justification for Ubuntu using a separate process for the past 6 years or so is documented in:
https://wiki.ubuntu.com/DesktopTeam/Bluetooth/BluezGit

Mostly it was because Debian was failing to release new BlueZ versions when I took over around 2017. And Ubuntu had already diverged from Debian in nontrivial ways. I've slowly been reducing the diff over time. That's a problem I did not create, but have been trying to solve, so please don't shoot the messenger.

If the Ubuntu process for this becomes contentious then I am happy for other people to own BlueZ and remove myself from ~bluetooth.