Am 16.02.26 um 11:40 PM schrieb Santiago Vila:
On Mon, Feb 16, 2026 at 10:36:02PM +0100, Alois Schlögl wrote:I believe this bug is due to the fact that debian/control is missing some build dependencies. Applying this patch should fix the issue. diff --git a/release/debian/control b/release/debian/control index 4ea71d8b..37223977 100644 --- a/release/debian/control +++ b/release/debian/control @@ -10,6 +10,8 @@ Build-Depends: debhelper-compat (= 13), d-shlibs, gawk, python3-setuptools, + python3-venv, + python3-build, python3-all-dev, python3-numpy, zlib1g-dev, Let me know if this is not the case. Then we can also enter a private conversation what the best a approach would be, to fix this.Hello. Version 3.9.2 is in salsa but it has not been uploaded yet. I tried the proposed patch on top of version 3.9.2 currently in salsa and this is what I got: * Creating isolated environment: venv+pip... The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command. apt install python3.13-venv You may need to use sudo with that command. After installing the python3-venv package, recreate your virtual environment. Failing command: /tmp/build-env-95wnng21/bin/python3.13 make[3]: *** [Makefile:17: sdist] Error 1 make[3]: Leaving directory '/build/reproducible-path/biosig-3.9.1/biosig4c++/python' make[3]: Entering directory '/build/reproducible-path/biosig-3.9.1/biosig4c++/python' python3.14 -m build --sdist * Creating isolated environment: venv+pip... The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command. apt install python3.14-venv I hope Andreas can fix this and complete the upload. (While I'm also a team member, I'm not confident enough yet to make uploads for new upstream releases). Thanks.
Hello Santiago, I'm not proficient in debian packaging, but what I can say is that ./configure && make && make install is supposed to build biosig for python for all python versions found with pyversions py3versions The is implemented in the top level Makefile.in of biosig. Could it be that the Debian package machinery in conflicting with this ? Cheers, Alois
