If this is really a bug in one of the build-depends,

Yes, fixed here:
https://github.com/neurodroid/stimfit/commit/36021a84

please use reassign and add an affects on src:stimfit, so that this is still visible in the BTS web page for this package.

I have prepared a new release: https://github.com/neurodroid/stimfit/commit/38ccfab9

I could upload this release to Debian Mentors. This is about where my Debian knowledge ends.

In your instructions, I do not understand the following terms:
“reassign”
“add an affects on src:stimfit”
“visible in the BTS web page”

If a simple upload to Debian Mentors does not address these issues, please provide step-by-step instructions.

Thank you

Kind regards
Christoph

On 12 Mar 2025, at 17:34, Santiago Vila <sanvila@debian.org> wrote:

Package: src:stimfit
Version: 0.16.6-1
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp
rm -rf ./.libs ./_libs ./.deps ./.stimfit
rm -rf /<<PKGBUILDDIR>>/man
find -name '*.o' | xargs -r rm -f
find -name '*.lo' | xargs -r rm -f
find -name '*.a' | xargs -r rm -f
find -name '*.la' | xargs -r rm -f
find -name '*.so' | xargs -r rm -f
rm -f /<<PKGBUILDDIR>>/test.h5
dh_clean
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f -- debian/stimfit.substvars debian/stimfit-dbg.substvars debian/python3-stfio.substvars debian/files
rm -fr -- debian/stimfit/ debian/tmp/ debian/stimfit-dbg/ debian/python3-stfio/
find . \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o -type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a \( -name autom4te.cache -o -name __pycache__ \) -prune -exec rm -rf {} + \) \)
debian/rules binary
dh_testdir
PYTHON=/usr/bin/python3.13 PYTHON_VERSION=3.13 ./configure --enable-python --enable-debian --with-biosig --prefix=/<<PKGBUILDDIR>>/debian/tmp/usr --with-wx-config="wx-config --toolkit=gtk3"
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style) checking dependency style of gcc... gcc3
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C preprocessor... gcc -E
checking for gawk... (cached) mawk
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for kernel... linux or similar
checking for C++ standard (boost is not required with c++17 and later) ... -std=gnu++17
checking for python3.13... /usr/bin/python3.13
checking for a version of Python >= '2.1.0'... yes
checking for the distutils Python package... no
configure: error: cannot import Python module "distutils".
Please check your Python installation. The error was:
Traceback (most recent call last):
File "<string>", line 1, in <module>
import distutils
ModuleNotFoundError: No module named 'distutils'
make: *** [debian/rules:48: install] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202503/

About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:stimfit, so that this is still
visible in the BTS web page for this package.

Thanks.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

El 12/3/25 a las 20:02, Christoph Schmidt-Hieber escribió:

In your instructions, I do not understand the following terms:
“reassign”
“add an affects on src:stimfit”
“visible in the BTS web page”

Those are terms used when dealing with the Debian bug system.
The full explanation may be found here:

https://www.debian.org/Bugs/server-control

Before reporting that stimfit does not build from source,
I look here to be sure that nobody reported it before:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=stimfit

If the real bug is not in stimfit, but instead
in one of the build-depends, the right thing to
do would be to reassign the bug to the package actually
making stimfit not to build ok.

However, the reassign operation makes the bug to
disappear from the above web page, and I would
not find it if I were looking for duplicates.

The "affects" operation tells the Debian bug system
that a bug in one package really affects another package,
and the outcome is that the bug is still shown in the
web page for the affected package.

Thanks.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 12 Mar 2025, at 20:21, Santiago Vila <sanvila@debian.org> wrote:

El 12/3/25 a las 20:02, Christoph Schmidt-Hieber escribió:

In your instructions, I do not understand the following terms:
“reassign”
“add an affects on src:stimfit”
“visible in the BTS web page”

Those are terms used when dealing with the Debian bug system.
The full explanation may be found here:

https://www.debian.org/Bugs/server-control

Before reporting that stimfit does not build from source,
I look here to be sure that nobody reported it before:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=stimfit

If the real bug is not in stimfit, but instead
in one of the build-depends, the right thing to
do would be to reassign the bug to the package actually
making stimfit not to build ok.

However, the reassign operation makes the bug to
disappear from the above web page, and I would
not find it if I were looking for duplicates.

The "affects" operation tells the Debian bug system
that a bug in one package really affects another package,
and the outcome is that the bug is still shown in the
web page for the affected package.

Thanks.

Thank you for the explanation. Now I understand your original message.
In fact the bug ist *not* in one of the build depends, it’s in stimfit so that
I do not have to do any of this reassignment magic.

I have prepared a new version of stimfit that closes this bug. If you can sponsor it, I could upload it to Debian mentors. Otherwise I’d contact one
of the other usual suspects.

Best wishes
Christoph

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)