This bug was fixed in the package bluez-alsa - 4.2.0-1
---
bluez-alsa (4.2.0-1) unstable; urgency=medium
[ Jochen Sprickerhof ]
* New upstream release.
* Drop debian/patches (merged upstream)
* Update d/copyright
* Use execute_before_dh_install in d/rules
* Install new man
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez-alsa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046047
Title:
Thanks for the reply, the actual problem is that it must be --with-
libopenaptx not --enable-libopenaptx as currently in the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046047
Title:
No
Hi, thanks for the reply. I now understand the licensing constraints.
Still, you should be aware that passing --enable-libopenaptx alone
appears to have no effect -- the configure logic that checks it is all
gated behind other flags.
The good news is that since I opened this bug, bluez-alsa added
From my understanding --enable-aptx and --enable-aptx-hd depend on
https://github.com/Arkq/openaptx which states in the readme:
This project is for research purposes only. Without a proper license
private and commercial usage might be a case of a patent infringement.
So we can't distribute it in
