On Mittwoch, 18. Dezember 2019 13:33:33 CET Stefan Seyfried wrote:
Am 18.12.19 um 12:10 schrieb Carlos E. R.:
On 18/12/2019 08.49, Stefan Seyfried wrote: He found that it (b-d in python3) has been removed, and the question is if that removal is related to this removal commented in the OP, or is unrelated.
I have no idea why python3 would ever have depended on bluez-devel, but I don't think this is related, but just "somebody" cleaned out old cruft from python3 spec files.
see the $SUBJECT: nothing about bluez-devel, just getting rid of deprecated tools.
Just to shed some light on why Python requires bluez-devel: Pythons 'socket' module has optional support for the AF_BLUETOOTH protocol family, but it is only enabled when bluez-devel is available during build. As socket is a dependency of many other modules it is built as part of python3-base. python3-base is a build dependency of many other packages, probably 2/3rd of all TW packages depend on it (directly or indirectly). Most importantly, python3-base is also a build dependency of bluez. The bluez-devel BuildRequires was moved from python3 to python3-base to make AF_BLUETOOTH available in pythons socket, but as it introduces a build loop it was removed again. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019