Your message dated Fri, 30 Oct 2026 11:03:47 +0100
with message-id <[email protected]>
and subject line Re: pygattlib: FTBFS against python 3.15rc2
has caused the Debian Bug report #1147231,
regarding pygattlib: FTBFS against python 3.15rc2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1147231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147231
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:pygattlib
Version: 0~20210616-1.1
User: [email protected]
Usertags: python3.15
Tags: patch, ftbfs, forky, sid
Severity: important
Hi!
While rebuilding the python related packages against the Python 3.15rc2
version we found that pygattlib fails to build from source [1].
To fix it, I backported upstream commit 73a73b71: Fix build for Python
3.13 [2].
I've applied the upstream fix in the sandbox [3] to verify that it
builds successfully, please consider applying the patch to support the
upcoming 3.15 version.
Setting the severity to important for now. Once Python 3.15 is released,
it will be added to python3-defaults and this bug will become release
critical.
Happy hacking,
[1]: https://debusine.debian.net/debian/r-python-python3.15/artifact/4284740/
[2]:
https://github.com/oscaracena/pygattlib/commit/73a73b71cfc139e1e0a08816fb976ff330c77ea5
[3]: https://debusine.debian.net/debian/r-python-python3.15/
--
"Can you imagine what I would do if I could do all I can?" -- Sun Tzu
Saludos /\/\ /\ >< `/
From 73a73b71cfc139e1e0a08816fb976ff330c77ea5 Mon Sep 17 00:00:00 2001
From: Gwyn Ciesla <[email protected]>
Date: Tue, 21 Nov 2023 16:33:21 -0600
Subject: [PATCH] Fix build for Python 3.13.
---
src/gattlib.cpp | 4 ----
1 file changed, 4 deletions(-)
diff --git a/src/gattlib.cpp b/src/gattlib.cpp
index 6a95ecb..bf9949e 100644
--- a/src/gattlib.cpp
+++ b/src/gattlib.cpp
@@ -96,10 +96,6 @@ IOService::IOService(bool run) {
void
IOService::start() {
- if (!PyEval_ThreadsInitialized()) {
- PyEval_InitThreads();
- }
-
boost::thread iothread(std::bind(&IOService::operator(), this));
start_event.wait(10);
}
--
--- End Message ---
--- Begin Message ---
¡Hola Alexandre!
El 2026-10-30 a las 07:34 +0100, Alexandre Detiste escribió:
I'm confused, quilt is confused:
the existing 36.patch has identical contents.
Interesting, looking at the information in here it seems that it was
caused by a bad build timing, an incomplete git repository history and
overlooks from my part to all of these.
So, the package failed to build with 3.15 as a supported version, that
queued the package for me to review it, the relevant error in the build
log is:
/usr/bin/x86_64-linux-gnu-ld.bfd: cannot find -lboost_python315: No such file
or directory
A rebuild of boost python wouid probably have fixed that.
But instead of focussing on that I went directly to the git repository,
rebuilt the package locally and found another problem that was causing
the package to fail to build aginst 3.13, without noticing that the git
repository was missing the latest nmu 0~20210616-1.1. By the time I
already had a boost library rebuilt against Python 3.15. So the
originnal problem was no longer present.
All of this is mostly my fault for fast tracking preparing the patches,
closing the bug.
My only pending request here is, if possible, please try to merge the
nmu in the git repository.
Happy hacking,
--
"It's a well-known fact that computing devices such as the abacus were
invented thousands of years ago. But it's not well known that the first use of
common computer protocol occurred in the Old Testament. This, of course, was
when Moses aborted the Egyptians' process with a control-sea."
-- Tom Galloway (recs.arts.comics, February 1992)
Saludos /\/\ /\ >< `/
signature.asc
Description: PGP signature
--- End Message ---