Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#997640: pybluez: FTBFS: error in PyBluez setup command: use_2to3 is invalid.
418 views
Skip to first unread message
Vasyl Gello
Nov 1, 2021, 6:00:04 AM11/1/21
to
Source: pybluez
Version: 0.23-3
Followup-For: Bug #997640
X-Debbugs-Cc: iwam...@debian.org, mat...@debian.org
tag -1 patch
Dear colleagues,
Since this issue puts the whole Kodi ecosystem I maintain at risk of
autoremoval from testing, I decided to modernize the package and
send the patch.
TO solve the build failure, I had to re-import the same source
tarball 0.23 with one upstream patch applied:
https://github.com/pybluez/pybluez/pull/414
Everyone expects the upstream release fixing this bug but from
reading upstream Github I have a feeling it will not happen anytime
soon.
Apart from re-packing the source tarball, I have bumped standards,
moved to debhelper-compat 13 and brushed the file structure of a
Debian package. I am attaching a debdiff with all the fixes.
I can also push the fix to Salsa if I am granted developer rights
at https://salsa.debian.org/bluetooth-team/pybluez or send three
MRs for every affected branch (master, upstream and pristine-tar).
Please let me know if you need more information.
Cheers,
Vasyl
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Version: 0.23-3
Followup-For: Bug #997640
X-Debbugs-Cc: iwam...@debian.org, mat...@debian.org
tag -1 patch
Dear colleagues,
Since this issue puts the whole Kodi ecosystem I maintain at risk of
autoremoval from testing, I decided to modernize the package and
send the patch.
TO solve the build failure, I had to re-import the same source
tarball 0.23 with one upstream patch applied:
https://github.com/pybluez/pybluez/pull/414
Everyone expects the upstream release fixing this bug but from
reading upstream Github I have a feeling it will not happen anytime
soon.
Apart from re-packing the source tarball, I have bumped standards,
moved to debhelper-compat 13 and brushed the file structure of a
Debian package. I am attaching a debdiff with all the fixes.
I can also push the fix to Salsa if I am granted developer rights
at https://salsa.debian.org/bluetooth-team/pybluez or send three
MRs for every affected branch (master, upstream and pristine-tar).
Please let me know if you need more information.
Cheers,
Vasyl
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
0 new messages