Bug#1075045: Prepared an NMU
Control: tag 1084603 + pending Control: tag 1075045 + pending I have prepared an NMU to fix this bug. It closes multiple bugs, so it is filed as a new bug, in #1087013. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1086578: sfepy FTBFS with Python >= 3.12: ModuleNotFoundError: No module named 'numpy.distutils'
Source: sfepy
Version: 2021.4-4
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, sfepy failed to rebuild.
numpy.distutils is deprecated and was removed when building with Python >= 3.12:
https://numpy.org/doc/2.1/reference/distutils.html#module-numpy.distutils
---
Command: dpkg-buildpackage --sanitize-env -us -uc -mDebusine Rebuild
-B -rfakeroot
dpkg-buildpackage: info: source package sfepy
dpkg-buildpackage: info: source version 2021.4-4+bd1
dpkg-buildpackage: info: source distribution sid
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture arm64
debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh_autoreconf_clean -O--buildsystem=pybuild
dh_clean -O--buildsystem=pybuild
debian/rules binary-arch
dh binary-arch --with python3 --buildsystem=pybuild
dh_update_autotools_config -a -O--buildsystem=pybuild
dh_autoreconf -a -O--buildsystem=pybuild
dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
Traceback (most recent call last):
File "/<>/setup.py", line 16, in
from build_helpers import (generate_a_pyrex_source, package_check, log,
File "/<>/build_helpers.py", line 26, in
from numpy.distutils.misc_util import appendpath
ModuleNotFoundError: No module named 'numpy.distutils'
E: pybuild pybuild:389: configure: plugin distutils failed with: exit code=1:
python3.12 setup.py config
dh_auto_configure: error: pybuild --configure -i python{version} -p 3.12
returned exit code 13
make: *** [debian/rules:8: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
Build finished at 2024-11-01T15:56:04Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/929920/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/42374/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1086577: amp FTBFS with python >= 3.12: No module named 'numpy.distutils'
Source: amp
Version: 0.6.1-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, amp failed to rebuild.
Probably related to #1067375, numpy.distutils is deprecated and was
removed when building with Python >= 3.12:
https://numpy.org/doc/2.1/reference/distutils.html#module-numpy.distutils
---
Command: dpkg-buildpackage --sanitize-env -us -uc -mDebusine Rebuild
-B -rfakeroot
dpkg-buildpackage: info: source package amp
dpkg-buildpackage: info: source version 0.6.1-1+bd1
dpkg-buildpackage: info: source distribution sid
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture arm64
fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
I: pybuild base:311: python3.12 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 4, in
from numpy.distutils.core import Extension, setup
ModuleNotFoundError: No module named 'numpy.distutils'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/setup.py", line 11, in
raise RuntimeError(msg)
RuntimeError: Please install numpy (version 1.7.0 or greater) before installing
Amp. (Amp uses numpy's installer so it can compile the fortran modules with
f2py.) You should be able to do this with a command like: $ pip install numpy
E: pybuild pybuild:389: clean: plugin distutils failed with: exit code=1:
python3.12 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.12 returned exit
code 13
make[1]: *** [debian/rules:34: override_dh_auto_clean] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:21: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit
status 2
Build finished at 2024-11-01T15:51:34Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/929918/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/42373/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1086007: FTBFS: undefined reference to `ompi_mpi_cxx_op_intercept' etc.
Source: lammps Version: 20240207+dfsg-1.1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, lammps failed to rebuild. --- [...] [100%] Linking CXX shared library liblammps.so /usr/bin/cmake -E cmake_link_script CMakeFiles/lammps.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-rpath -Wl,/usr/lib/aarch64-linux-gnu/openmpi/lib -Wl,-z,relro -shared -Wl,-soname,liblammps.so.0 -o liblammps.so.0 @CMakeFiles/lammps.dir/objects1.rsp -Wl,-rpath,/usr/lib/aarch64-linux-gnu/openmpi/lib:/usr/lib/aarch64-linux-gnu/hdf5/serial: /usr/lib/aarch64-linux-gnu/libjpeg.so /usr/lib/aarch64-linux-gnu/libpng.so /usr/lib/aarch64-linux-gnu/libz.so /usr/lib/aarch64-linux-gnu/libfftw3.so /usr/lib/aarch64-linux-gnu/libfftw3_omp.so /usr/lib/aarch64-linux-gnu/libpython3.12.so /usr/lib/aarch64-linux-gnu/libvoro++.so /usr/lib/aarch64-linux-gnu/libnetcdf.so /usr/lib/aarch64-linux-gnu/libpnetcdf.so /usr/lib/aarch64-linux-gnu/libvtkIOParallelXML-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libcurl.so /usr/lib/aarch64-linux-gnu/libkim-api.so.2.3.0 /usr/lib/aarch64-linux-gnu/libz.so -lm liblammps_poems.a liblammps_atc.a liblammps_awpmd.a liblammps_h5md.a /usr/lib/aarch64-linux-gnu/liblapack.so /usr/lib/aarch64-linux-gnu/libblas.so /usr/lib/aarch64-linux-gnu/libblas.so -ldl /usr/lib/gcc/aarch64-linux-gnu/14/libgomp.so /usr/lib/aarch64-linux-gnu/libnetcdf.so /usr/lib/aarch64-linux-gnu/libvtkIOXML-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkIOXMLParser-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkIOLegacy-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkIOCore-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkCommonExecutionModel-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkCommonDataModel-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkCommonTransforms-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkCommonMath-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkkissfft-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libvtkCommonCore-9.3.so.9.3 /usr/lib/aarch64-linux-gnu/libtbb.so.12.12 /usr/lib/aarch64-linux-gnu/libvtksys-9.3.so.9.3 -ldl /usr/lib/aarch64-linux-gnu/libzstd.so /usr/lib/aarch64-linux-gnu/openmpi/lib/libmpi.so /usr/lib/aarch64-linux-gnu/hdf5/serial/libhdf5.so /usr/lib/aarch64-linux-gnu/libcrypto.so /usr/lib/aarch64-linux-gnu/libcurl.so /usr/lib/aarch64-linux-gnu/libpthread.a /usr/lib/aarch64-linux-gnu/libsz.so /usr/lib/aarch64-linux-gnu/libz.so /usr/lib/aarch64-linux-gnu/libdl.a -lm /usr/bin/cmake -E cmake_symlink_library liblammps.so.0 liblammps.so.0 liblammps.so make[3]: Leaving directory '/<>/debian/build' [100%] Built target lammps make -f CMakeFiles/lmp.dir/build.make CMakeFiles/lmp.dir/depend make[3]: Entering directory '/<>/debian/build' cd /<>/debian/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<>/cmake /<>/cmake /<>/debian/build /<>/debian/build /<>/debian/build/CMakeFiles/lmp.dir/DependInfo.cmake "--color=" make[3]: Leaving directory '/<>/debian/build' make -f CMakeFiles/lmp.dir/build.make CMakeFiles/lmp.dir/build make[3]: Entering directory '/<>/debian/build' [100%] Building CXX object CMakeFiles/lmp.dir/<>/src/main.cpp.o /usr/bin/c++ -DLAMMPS_SMALLBIG -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX -D_MPICC_H -I/<>/src -I/<>/debian/build/includes -isystem /usr/lib/aarch64-linux-gnu/openmpi/include -isystem /usr/lib/aarch64-linux-gnu/openmpi/include/openmpi -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fPIE -fopenmp -MD -MT CMakeFiles/lmp.dir/<>/src/main.cpp.o -MF CMakeFiles/lmp.dir/<>/src/main.cpp.o.d -o CMakeFiles/lmp.dir/<>/src/main.cpp.o -c /<>/src/main.cpp [100%] Linking CXX executable lmp /usr/bin/cmake -E cmake_link_script CMakeFiles/lmp.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-rpath -Wl,/usr/lib/aarch64-linux-gnu/openmpi/lib "CMakeFiles/lmp.dir/<>/src/main.cpp.o" -o lmp -Wl,-rpath,/<>/debian/build:/usr/lib/aarch64-linux-gnu/openmpi/lib: liblammps.so.0 /usr/lib/aarch64-linux-gnu/openmpi/lib/libmpi.so /usr/lib/gcc/aarch64-linux-gnu/14/libgomp.so /usr/lib/aarch64-linux-gnu/libpthread.a /usr/bin/ld: warning: libmpi_cxx.so.40, needed by /lib/aarch64-linux-gnu/libpnetcdf.so.0d, not found (try using -rpath or -rpath-link) /usr/bin/ld: /lib/aarch64-linux-gnu/libpnetcdf.so.0d: undefined reference to `ompi_mpi_cxx_op_intercept' /usr/bin/ld: /lib/aarch64-linux-gnu/libpnetcdf.so.0d: undefined reference to `MPI::Win::Free()' /usr/bin/ld: /lib/aarch64-linux-gnu/libpnetcdf.so.0d: undefine
Bug#1086010: FTBFS with GCC-14
Source: subvertpy Version: 0.11.0-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, subvertpy failed to rebuild. --- [...] 9bKZ7HsvgN2bSkvQmIObThKfbbtvkb4Xt6MNux0Y5b6y3TyExbHfpFQGKnnKvCny z1Qcajq/CWma9RnG98pdUrsu0VB+a54t3jN+iGdQnx9wqAXREUuYxlGKshi/olSo IoFZEg3NgaAo2R3eXGkERmwRT4jKDbH+ZSJrfVNXaeykJ4YwkkXUHlXnAlrWMnrQ BqqwQvGg93DiK07PuKqqmatcySt8OXyrTlGMOjW+Z8D6BVOhL4mwjyi6C3sTNiBq xNe9JZYpwSG1WEXmt7bty64lTE2J2WFr6unrA8gqvyF/K6UxaqS9OiZGtNveuRas Q92kF3Q7WVTChmGPufJ06gsWi28zRHWkCU6QWt8HULIuHLmbd7Q= =7u6M -END PGP SIGNATURE- gpgv: Signature made Mon Jan 11 03:07:11 2021 UTC gpgv:using RSA key B23862C415D6565A4E86CBD7579C160D4C9E23E8 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./subvertpy_0.11.0-1.dsc: no acceptable signature found dpkg-source: info: extracting subvertpy in /<> dpkg-source: info: unpacking subvertpy_0.11.0.orig.tar.gz dpkg-source: info: unpacking subvertpy_0.11.0-1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying compat-api.patch Check disk space Sufficient free space for build Hack binNMU version --- Created changelog entry for binNMU version 0.11.0-1+bd1 User Environment APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/sbuild-nonexistent LANG=en_US.UTF-8 LC_ALL=C.UTF-8 LOGNAME=debusine-worker OLDPWD=/ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games PWD=/<> SHELL=/bin/sh USER=debusine-worker dpkg-buildpackage - Command: dpkg-buildpackage --sanitize-env -us -uc -mDebusine Rebuild -B -rfakeroot dpkg-buildpackage: info: source package subvertpy dpkg-buildpackage: info: source version 0.11.0-1+bd1 dpkg-buildpackage: info: source distribution sid dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 dpkg-source: info: using options from subvertpy-0.11.0/debian/source/options: --extend-diff-ignore=^\.travis.yml$ debian/rules clean CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CFLAGS="-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard" CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard" \ LDFLAGS="-Wl,-z,relro" dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py clean running clean removing '/<>/.pybuild/cpython3_3.12_subvertpy/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.12' does not exist -- can't clean it dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary-arch CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CFLAGS="-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard" CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard" \ LDFLAGS="-Wl,-z,relro" dh binary-arch --with python3 --buildsystem=pybuild dh_update_autotools_config -a -O--buildsystem=pybuild dh_autoreconf -a -O--buildsystem=pybuild dh_auto_configure -a -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config running config dh_auto_build -a -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy copying subvertpy/delta.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy copying subvertpy/marshall.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy copying subvertpy/__init__.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy copying subvertpy/server.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy copying subvertpy/ra_svn.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy copying subvertpy/properties.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy copying subvertpy/ra.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy creating /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy/tests copying subvertpy/tests/test_delta.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy/tests copying subvertpy/tests/test_marshall.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy/tests copying subvertpy/tests/test_ra.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy/tests copying subvertpy/tests/test_properties.py -> /<>/.pybuild/cpython3_3.12_subvertpy/build/subvertpy/tests copying subvertpy/tests/_
Bug#1086006: python-blosc FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/pydata_sphinx_theme/theme/pydata_sphinx_theme'
Source: python-blosc Version: 1.11.2+ds1-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, python-blosc failed to rebuild. --- [...] Not searching for unused variables given on the command line. -- The C compiler identification is GNU 14.2.0 -- The CXX compiler identification is GNU 14.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Warning (dev) at /usr/lib/python3/dist-packages/skbuild/resources/cmake/FindPythonExtensions.cmake:245 (find_package): Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules are removed. Run "cmake --help-policy CMP0148" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Call Stack (most recent call first): CMakeLists.txt:3 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Found PythonInterp: /usr/bin/python3.12 (found version "3.12.7") CMake Warning (dev) at /usr/lib/python3/dist-packages/skbuild/resources/cmake/FindPythonExtensions.cmake:252 (find_package): Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules are removed. Run "cmake --help-policy CMP0148" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Call Stack (most recent call first): CMakeLists.txt:3 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Found PythonLibs: /usr/lib/aarch64-linux-gnu/libpython3.12.so (found version "3.12.7") CMake Warning (dev) at blosc/CMakeLists.txt:5 (find_package): Policy CMP0074 is not set: find_package uses _ROOT variables. Run "cmake --help-policy CMP0074" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMake variable Blosc_ROOT is set to: /usr/lib/libblosc For compatibility, CMake is ignoring the variable. This warning is for project developers. Use -Wno-dev to suppress it. -- Found Blosc library: /usr/lib/aarch64-linux-gnu/libblosc.so -- Performing Test Weak Link MODULE -> SHARED (gnu_ld_ignore) - Success _modinit_prefix:PyInit_ -- Configuring done (1.8s) -- Generating done (0.0s) -- Build files have been written to: /<>/_skbuild/linux-aarch64-3.12/cmake-build gmake[2]: Entering directory '/<>/_skbuild/linux-aarch64-3.12/cmake-build' gmake[3]: Entering directory '/<>/_skbuild/linux-aarch64-3.12/cmake-build' gmake[4]: Entering directory '/<>/_skbuild/linux-aarch64-3.12/cmake-build' gmake[4]: Leaving directory '/<>/_skbuild/linux-aarch64-3.12/cmake-build' gmake[4]: Entering directory '/<>/_skbuild/linux-aarch64-3.12/cmake-build' [ 50%] Building C object blosc/CMakeFiles/blosc_extension.dir/blosc_extension.c.o [100%] Linking C shared module blosc_extension.cpython-312-aarch64-linux-gnu.so gmake[4]: Leaving directory '/<>/_skbuild/linux-aarch64-3.12/cmake-build' [100%] Built target blosc_extension gmake[3]: Leaving directory '/<>/_skbuild/linux-aarch64-3.12/cmake-build' Install the project... -- Install configuration: "Release" -- Installing: /<>/_skbuild/linux-aarch64-3.12/cmake-install/blosc/blosc_extension.cpython-312-aarch64-linux-gnu.so gmake[2]: Leaving directory '/<>/_skbuild/linux-aarch64-3.12/cmake-build' copying blosc/version.py -> _skbuild/linux-aarch64-3.12/cmake-install/blosc/version.py copying blosc/__init__.py -> _skbuild/linux-aarch64-3.12/cmake-install/blosc/__init__.py copying blosc/_version.py -> _skbuild/linux-aarch64-3.12/cmake-install/blosc/_version.py copying blosc/test.py -> _skbuild/linux-aarch64-3.12/cmake-install/blosc/test.py copying blosc/toplevel.py -> _skbuild/linux-aarch64-3.12/cmake-install/blosc/toplevel.py /usr/lib/python3/dist-packages/setuptools/__init__.py:94: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. !! dist.fetch_build_eggs(dist.setup_requires) /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require' warnings.warn(msg) running build running build_py creating _skbuild/linux-aarch64-3.12/setuptools/lib.linux-aarch64-cpython-312/blosc copying _skbuild/linux-aarch64-3.12/cmake-install/blosc/version.py -> _skbuild/linux-aarch64-3.12/
Bug#1084247: marked as pending in distro-info
Control: tag -1 pending Hello, Bug #1084247 in distro-info reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/distro-info/-/commit/a5e63d8a6d680d3fe0e51aaac9e280f4a7617fc2 Bump pylint minimum version. (Closes: #1084247) (this message was generated automatically) -- Greetings https://bugs.debian.org/1084247
Bug#1084247: closed by Debian FTP Masters (reply to Benjamin Drung ) (Bug#1084247: fixed in distro-info 1.10)
Hi Colin (2024.10.11_08:11:08_-0700) > Maybe the simplest option would be to have the relevant > debian/tests/control stanza depend on pylint (>= 3.3.0)? That should > hint things into understanding that the two packages need to be tested > together. Yeah, I'll do that. Having pylint in package tests has been much more pain that it's worth, I think having it in GitLab CI only would be preferable. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1084732: skimage FTBFS with Python 3.13
Source: skimage Version: 0.24.0-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: python3.13 Forwarded: https://github.com/scikit-image/scikit-image/pull/7448 This package failed build from source when test-built against a version of python3-defaults that includes 3.13 as a supported version. To reproduce this issue, build against python3-defaults (python3-all-dev etc.) from Debian experimental. What's new in Python 3.13: https://docs.python.org/3.13/whatsnew/3.13.html Log snippet: = test session starts == platform linux -- Python 3.13.0rc3, pytest-8.3.3, pluggy-1.5.0 rootdir: /<>/.pybuild/cpython3_3.13/build configfile: pyproject.toml plugins: typeguard-4.3.0, doctestplus-1.2.1 collected 8611 items / 2 errors / 5 skipped ERRORS ___ ERROR collecting skimage/draw/tests/test_draw.py ___ skimage/draw/tests/test_draw.py:24: in from skimage.measure import regionprops :1412: in _handle_fromlist ??? /usr/lib/python3/dist-packages/lazy_loader/__init__.py:82: in __getattr__ submod = importlib.import_module(submod_path) /usr/lib/python3.13/importlib/__init__.py:88: in import_module return _bootstrap._gcd_import(name[level:], package, level) skimage/measure/_regionprops.py:1426: in _install_properties_docs() skimage/measure/_regionprops.py:1421: in _install_properties_docs getattr(RegionProperties, p).__doc__ = prop_doc[p] E KeyError: 'area_bbox' __ ERROR collecting skimage/measure/tests/test_regionprops.py __ skimage/measure/tests/test_regionprops.py:17: in from skimage.measure._regionprops import ( skimage/measure/_regionprops.py:1426: in _install_properties_docs() skimage/measure/_regionprops.py:1421: in _install_properties_docs getattr(RegionProperties, p).__doc__ = prop_doc[p] E KeyError: 'area_bbox' === short test summary info If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/836301/ This bug has been filed at "normal" severity, as we haven't started the transition to add 3.13 as a supported version, yet. This will be raised to RC as soon as that happens, hopefully well before trixie. Thanks, Stefano
Bug#1084228: FTBFS: Test failure: test_array_inference[data7-expected7]: AssertionError: DatetimeArray._ndarray are different
Source: pandas Version: 2.2.3+dfsg-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, pandas failed to rebuild. --- [...] = test session starts == platform linux -- Python 3.12.7, pytest-8.3.3, pluggy-1.5.0 PyQt5 5.15.11 -- Qt runtime 5.15.13 -- Qt compiled 5.15.13 rootdir: /<>/.pybuild/cpython3_3.12/build configfile: pyproject.toml plugins: qt-4.3.1, localserver-0.0.0, xdist-3.6.1, typeguard-4.3.0, hypothesis-6.112.1, asyncio-0.24.0a1, forked-1.6.0 asyncio: mode=Mode.STRICT, default_loop_scope=None collected 19229 items / 2 skipped pandas/tests/arrays/boolean/test_arithmetic.py . pandas/tests/arrays/boolean/test_astype.py ... pandas/tests/arrays/boolean/test_comparison.py pandas/tests/arrays/boolean/test_construction.py . pandas/tests/arrays/boolean/test_function.py ... pandas/tests/arrays/boolean/test_indexing.py ... pandas/tests/arrays/boolean/test_logical.py ... pandas/tests/arrays/boolean/test_ops.py .. pandas/tests/arrays/boolean/test_reduction.py .. pandas/tests/arrays/boolean/test_repr.py . pandas/tests/arrays/categorical/test_algos.py .. pandas/tests/arrays/categorical/test_analytics.py x..x pandas/tests/arrays/categorical/test_api.py . pandas/tests/arrays/categorical/test_astype.py .. pandas/tests/arrays/categorical/test_constructors.py ... pandas/tests/arrays/categorical/test_dtypes.py .. pandas/tests/arrays/categorical/test_indexing.py ... pandas/tests/arrays/categorical/test_map.py . pandas/tests/arrays/categorical/test_missing.py .. pandas/tests/arrays/categorical/test_operators.py .. pandas/tests/arrays/categorical/test_replace.py .. pandas/tests/arrays/categorical/test_repr.py ... pandas/tests/arrays/categorical/test_sorting.py pandas/tests/arrays/categorical/test_subclass.py ... pandas/tests/arrays/categorical/test_take.py pandas/tests/arrays/categorical/test_warnings.py s pandas/tests/arrays/datetimes/test_constructors.py ..ss pandas/tests/arrays/datetimes/test_cumulative.py ... pandas/tests/arrays/datetimes/test_reductions.py . pandas/tests/arrays/floating/test_arithmetic.py .. pandas/tests/arrays/floating/test_astype.py . pandas/tests/arrays/floating/test_comparison.py .. pandas/tests/arrays/floating/test_concat.py ... pandas/tests/arrays/floating/test_construction.py ... pandas/tests/arrays/floating/test_contains.py . pandas/tests/arrays/floating/test_function.py pandas/tests/arrays/floating/test_repr.py pandas/tests/arrays/floating/test_to_numpy.py .. pandas/tests/arrays/integer/test_arithmetic.py ... pandas/tests/arrays/integer/test_comparison.py . pandas/tests/arrays/integer/test_concat.py .. pandas/tests/arrays/integer/test_construction.py ...
Bug#1084213: FTBFS: :: Fatal: GES: Skipping foreign identifier 'GstFrameCompositionApi' from namespace GstPbutils
Source: gstreamer-editing-services1.0
Version: 1.24.8-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, gstreamer-editing-services1.0 failed to rebuild.
---
[...]
[191/217] env
PKG_CONFIG_PATH=/<>/obj-aarch64-linux-gnu/meson-uninstalled
PKG_CONFIG=/usr/bin/pkg-config CC=cc /usr/bin/aarch64-linux-gnu-g-ir-scanner
--quiet --no-libtool --namespace=GES --nsversion=1.0 --warn-all --output
ges/GES-1.0.gir '--add-init-section=extern void gst_init(gint*,gchar**);extern
void ges_init(void);g_setenv("GST_REGISTRY_1.0", "/no/way/this/exists.reg",
TRUE);g_setenv("GST_PLUGIN_PATH_1_0", "",
TRUE);g_setenv("GST_PLUGIN_SYSTEM_PATH_1_0", "", TRUE);g_setenv("GST_DEBUG",
"0", TRUE);gst_init(NULL,NULL);ges_init();' --quiet --c-include=ges/ges.h
-I/<>/ges -I/<>/obj-aarch64-linux-gnu/ges
-I/<>/. -I/<>/obj-aarch64-linux-gnu/.
--filelist=/<>/obj-aarch64-linux-gnu/ges/libges-1.0.so.0.2408.0.p/GES_1.0_gir_filelist
--include=Gst-1.0 --include=GstPbutils-1.0 --include=GstVideo-1.0
--include=Gio-2.0 --include=GObject-2.0 --symbol-prefix=ges
--identifier-prefix=GES --pkg-export=gst-editing-services-1.0 --cflags-begin
-I/<>/. -I/<>/obj-aarch64-linux-gnu/.
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0
-I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6
-I/usr/include/aarch64-linux-gnu -I/usr/include/orc-0.4 -I/usr/include/libmount
-I/usr/include/blkid -I/usr/include/libxml2
-I/usr/include/gobject-introspection-1.0 --cflags-end
--add-include-path=/usr/share/gir-1.0
-L/<>/obj-aarch64-linux-gnu/ges --library ges-1.0
--extra-library=gstreamer-1.0 --extra-library=gobject-2.0
--extra-library=glib-2.0 --extra-library=gstbase-1.0
--extra-library=gstvideo-1.0 --extra-library=gstpbutils-1.0
--extra-library=gstaudio-1.0 --extra-library=gstcontroller-1.0
--extra-library=gio-2.0 --extra-library=xml2 --extra-library=m
--extra-library=python3.12 --extra-library=gmodule-2.0 --extra-library=dl
--extra-library=girepository-1.0 --sources-top-dirs /<>/
--sources-top-dirs /<>/obj-aarch64-linux-gnu/
FAILED: ges/GES-1.0.gir·
env PKG_CONFIG_PATH=/<>/obj-aarch64-linux-gnu/meson-uninstalled
PKG_CONFIG=/usr/bin/pkg-config CC=cc /usr/bin/aarch64-linux-gnu-g-ir-scanner
--quiet --no-libtool --namespace=GES --nsversion=1.0 --warn-all --output
ges/GES-1.0.gir '--add-init-section=extern void gst_init(gint*,gchar**);extern
void ges_init(void);g_setenv("GST_REGISTRY_1.0", "/no/way/this/exists.reg",
TRUE);g_setenv("GST_PLUGIN_PATH_1_0", "",
TRUE);g_setenv("GST_PLUGIN_SYSTEM_PATH_1_0", "", TRUE);g_setenv("GST_DEBUG",
"0", TRUE);gst_init(NULL,NULL);ges_init();' --quiet --c-include=ges/ges.h
-I/<>/ges -I/<>/obj-aarch64-linux-gnu/ges
-I/<>/. -I/<>/obj-aarch64-linux-gnu/.
--filelist=/<>/obj-aarch64-linux-gnu/ges/libges-1.0.so.0.2408.0.p/GES_1.0_gir_filelist
--include=Gst-1.0 --include=GstPbutils-1.0 --include=GstVideo-1.0
--include=Gio-2.0 --include=GObject-2.0 --symbol-prefix=ges
--identifier-prefix=GES --pkg-export=gst-editing-services-1.0 --cflags-begin
-I/<>/. -I/<>/obj-aarch64-linux-gnu/.
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0
-I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6
-I/usr/include/aarch64-linux-gnu -I/usr/include/orc-0.4 -I/usr/include/libmount
-I/usr/include/blkid -I/usr/include/libxml2
-I/usr/include/gobject-introspection-1.0 --cflags-end
--add-include-path=/usr/share/gir-1.0
-L/<>/obj-aarch64-linux-gnu/ges --library ges-1.0
--extra-library=gstreamer-1.0 --extra-library=gobject-2.0
--extra-library=glib-2.0 --extra-library=gstbase-1.0
--extra-library=gstvideo-1.0 --extra-library=gstpbutils-1.0
--extra-library=gstaudio-1.0 --extra-library=gstcontroller-1.0
--extra-library=gio-2.0 --extra-library=xml2 --extra-library=m
--extra-library=python3.12 --extra-library=gmodule-2.0 --extra-library=dl
--extra-library=girepository-1.0 --sources-top-dirs /<>/
--sources-top-dirs /<>/obj-aarch64-linux-gnu/
:: Fatal: GES: Skipping foreign identifier 'GstFrameCompositionApi'
from namespace GstPbutils
:: Fatal: GES: Skipping foreign identifier 'GstFrameCompositionApi'
from namespace GstPbutils
[...]
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 ninja -j16 -v
returned exit code 1
make: *** [debian/rules:17: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch 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 (for the next 30 days):
https://debusine.debian.net/artifact/834413/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/40769/
If this is really a
Bug#1084148: FTBFS: tests abort in pysph/base/tests/test_nnps.py
Source: pysph
Version: 1.0~b1-8
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, pysph failed to rebuild.
---
[...]
dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:311: cd '/<>/.pybuild/cpython3_3.12/build';
python3.12 -m pytest -k "not test_sph_evaluator and not TestInterpolator and
not test_get_points_from_mgrid and not test_get_surface_points_uniform and not
test_compressed_octree_has_lesser_depth_than_octree and not
test_parallel_compressed_octree_has_lesser_depth_than_parallel_octree and not
test_ldcavity_example"
= test session starts ==
platform linux -- Python 3.12.7, pytest-8.3.3, pluggy-1.5.0
rootdir: /<>
configfile: tox.ini
plugins: typeguard-4.3.0
collected 1036 items / 121 deselected / 915 selected
pysph/base/tests/test_device_helper.py ..s..s..s..s..s..s..s..s..s..s..s [ 3%]
..s..s..s..s..s..s..s. [ 6%]
pysph/base/tests/test_domain_manager.py [ 7%]
pysph/base/tests/test_kernel.py [ 11%]
.[ 18%]
pysph/base/tests/test_linalg3.py ... [ 19%]
pysph/base/tests/test_neighbor_cache.py [ 20%]
pysph/base/tests/test_nnps.py ...Aborted
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=134: cd
'/<>/.pybuild/cpython3_3.12/build'; python3.12 -m pytest -k "not
test_sph_evaluator and not TestInterpolator and not test_get_points_from_mgrid
and not test_get_surface_points_uniform and not
test_compressed_octree_has_lesser_depth_than_octree and not
test_parallel_compressed_octree_has_lesser_depth_than_parallel_octree and not
test_ldcavity_example"
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12
returned exit code 13
make: *** [debian/rules:18: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
Build finished at 2024-10-05T17:34:59Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/832066/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/40740/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1084147: FTBFS: test failure: IsADirectoryError: [Errno 21] Is a directory: '/tmp/tmps0c41yfa'
Source: python-openstacksdk Version: 3.0.0-3 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, python-openstacksdk failed to rebuild. --- [...] openstack.tests.unit.test_resource.TestWaitForDelete.test_callback_without_progress ... ok openstack.tests.unit.test_resource.TestWaitForDelete.test_status openstack.tests.unit.test_resource.TestWaitForDelete.test_status ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_callback_without_progress openstack.tests.unit.test_resource.TestWaitForStatus.test_callback_without_progress ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_immediate_status openstack.tests.unit.test_resource.TestWaitForStatus.test_immediate_status ... ok openstack.tests.unit.test_resource.TestWaitForDelete.test_success_not_found openstack.tests.unit.test_resource.TestWaitForDelete.test_success_not_found ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_immediate_status_case openstack.tests.unit.test_resource.TestWaitForStatus.test_immediate_status_case ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_immediate_status_different_attribute openstack.tests.unit.test_resource.TestWaitForStatus.test_immediate_status_different_attribute ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_no_sleep openstack.tests.unit.test_resource.TestWaitForStatus.test_no_sleep ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_status_fails openstack.tests.unit.test_resource.TestWaitForStatus.test_status_fails ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_status_fails_different_attribute openstack.tests.unit.test_resource.TestWaitForStatus.test_status_fails_different_attribute ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_status_match openstack.tests.unit.test_resource.TestWaitForStatus.test_status_match ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_status_match_different_attribute openstack.tests.unit.test_resource.TestWaitForStatus.test_status_match_different_attribute ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_status_match_none openstack.tests.unit.test_resource.TestWaitForStatus.test_status_match_none ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_status_match_with_none openstack.tests.unit.test_resource.TestWaitForStatus.test_status_match_with_none ... ok openstack.tests.unit.test_resource.TestWaitForStatus.test_timeout openstack.tests.unit.test_resource.TestWaitForStatus.test_timeout ... ok openstack.tests.unit.test_resource.TestWaitForDelete.test_timeout openstack.tests.unit.test_resource.TestWaitForDelete.test_timeout ... ok openstack.tests.unit.test_resource.Test_Request.test_create openstack.tests.unit.test_resource.Test_Request.test_create ... ok openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_not_supported_no_default openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_not_supported_no_default ... ok openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_not_supported_no_default_exception openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_not_supported_no_default_exception ... ok openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_equal_default openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_equal_default ... ok openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_higher_default openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_higher_default ... ok openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_lower_default openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_lower_default ... ok openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_lower_default_exception openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_lower_default_exception ... ok openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_no_default openstack.tests.unit.test_utils.TestSupportsMicroversion.test_requested_supported_no_default ... ok openstack.tests.unit.test_utils.TestSupportsMicroversion.test_require_microversion openstack.tests.unit.test_utils.TestSupportsMicroversion.test_require_microversion ... ok openstack.tests.unit.test_utils.TestTinyDAG.test_walk_raise openstack.tests.unit.test_utils.TestTinyDAG.test_walk_raise ... ok openstack.tests.unit.workflow.test_version.TestVersion.test_basic openstack.tests.unit.workflow.test_version.TestVersion.test_basic ... ok openstack.tests.unit.workflow.test_version.TestVersion.test_make_it openstack.tests.unit.workflow.test_version.TestVersion.test_make_it ... ok openstack.tests.unit.workflow.test_workflow.TestWorkflow.test_basic o
Bug#1084096: libxml2 FTBFS with Python 3.13
Source: libxml2
Version: 2.12.7+dfsg+really2.9.14-0.1
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: python3.13
This package failed build from source when test-built against a version of
python3-defaults that includes 3.13 as a supported version.
To reproduce this issue, build against python3-defaults (python3-all-dev etc.)
from Debian experimental.
What's new in Python 3.13:
https://docs.python.org/3.13/whatsnew/3.13.html
Log snippet:
| ^
| PyObject_CallMethod
../../../python/libxml.c:260:9: error: assignment to 'PyObject *' {aka 'struct
_object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
260 | ret = PyEval_CallMethod(file, (char *) "close", (char *) "()");
| ^
../../../python/libxml.c: In function 'xmlPythonFileReadRaw':
../../../python/libxml.c:290:9: error: assignment to 'PyObject *' {aka 'struct
_object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
290 | ret = PyEval_CallMethod(file, (char *) "read", (char *) "(i)", len);
| ^
../../../python/libxml.c: In function 'xmlPythonFileRead':
../../../python/libxml.c:355:9: error: assignment to 'PyObject *' {aka 'struct
_object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
355 | ret = PyEval_CallMethod(file, (char *) "io_read", (char *) "(i)",
len);
| ^
../../../python/libxml.c: In function 'xmlPythonFileWrite':
../../../python/libxml.c:423:13: error: assignment to 'PyObject *' {aka 'struct
_object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
423 | ret = PyEval_CallMethod(file, (char *) "io_write", (char *)
"(O)",
| ^
../../../python/libxml.c:426:13: error: assignment to 'PyObject *' {aka 'struct
_object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
426 | ret = PyEval_CallMethod(file, (char *) "write", (char *) "(O)",
| ^
../../../python/libxml.c: In function 'xmlPythonFileClose':
../../../python/libxml.c:462:13: error: assignment to 'PyObject *' {aka 'struct
_object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
462 | ret = PyEval_CallMethod(file, (char *) "io_close", (char *)
"()");
| ^
../../../python/libxml.c:464:13: error: assignment to 'PyObject *' {aka 'struct
_object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
464 | ret = PyEval_CallMethod(file, (char *) "flush", (char *) "()");
| ^
../../../python/types.c: In function 'libxml_PyFileGet':
../../../python/types.c:86:14: warning: unused variable 'w_fh'
[-Wunused-variable]
86 | intptr_t w_fh = -1;
| ^~~~
../../../python/libxml.c: In function 'libxml_xmlErrorFuncHandler':
../../../python/libxml.c:1650:43: warning: pointer targets in passing argument
1 of 'libxml_charPtrConstWrap' differ in signedness [-Wpointer-sign]
1650 | message = libxml_charPtrConstWrap(ptr);
| ^~~
| |
| unsigned char *
In file included from ../../../python/libxml.c:29:
../../../python/libxml_wrap.h:240:48: note: expected 'const char *' but
argument is of type 'unsigned char *'
240 | PyObject * libxml_charPtrConstWrap(const char *str);
|^~~
../../../python/libxml.c:1652:18: error: implicit declaration of function
'PyEval_CallObject'; did you mean 'PyObject_CallObject'?
[-Wimplicit-function-declaration]
1652 | result = PyEval_CallObject(libxml_xmlPythonErrorFuncHandler,
list);
| ^
| PyObject_CallObject
../../../python/libxml.c:1652:16: error: assignment to 'PyObject *' {aka
'struct _object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
1652 | result = PyEval_CallObject(libxml_xmlPythonErrorFuncHandler,
list);
|^
../../../python/libxml.c: In function
'libxml_xmlParserCtxtGenericErrorFuncHandler':
../../../python/libxml.c:1742:12: error: assignment to 'PyObject *' {aka
'struct _object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
1742 | result = PyEval_CallObject(pyCtxt->f, list);
|^
../../../python/libxml.c: In function
'libxml_xmlValidCtxtGenericErrorFuncHandler':
../../../python/libxml.c:1928:12: error: assignment to 'PyObject *' {aka
'struct _object *'} from 'int' makes pointer from integer without a cast
[-Wint-conversion]
1928 | result = PyEval_CallObject(pyCtxt->error, list);
|^
../../../python/libxml.c: In function
'libxml_xmlValidCtxtGenericWarningFuncHandler':
../../../python/libxml
Bug#1082397: FTBFS: test_setuptools_prepare_metadata_for_build_wheel: AssertionError: assert ['magic>3', 'requests>2'] == ['magic >3', 'requests >2']
Source: pyproject-api
Version: 1.7.1-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, pyproject-api failed to rebuild.
---
[...]
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build;
python3.12 -m pytest tests
= test session starts ==
platform linux -- Python 3.12.6, pytest-8.3.3, pluggy-1.5.0
rootdir: /<>/.pybuild/cpython3_3.12/build
configfile: pyproject.toml
plugins: typeguard-4.3.0, cov-5.0.0, mock-3.14.0
collected 59 items
tests/test_backend.py [ 13%]
tests/test_frontend.py . [ 62%]
tests/test_frontend_setuptools.py ..F... [ 79%]
tests/test_main.py ... [ 91%]
tests/test_util.py [ 98%]
tests/test_version.py . [100%]
=== FAILURES ===
___ test_setuptools_prepare_metadata_for_build_wheel ___
frontend_setuptools =
tmp_path =
PosixPath('/tmp/pytest-of-debusine-worker/pytest-0/test_setuptools_prepare_metada0')
def test_setuptools_prepare_metadata_for_build_wheel(frontend_setuptools:
SubprocessFrontend, tmp_path: Path) -> None:
meta = tmp_path / "meta"
result =
frontend_setuptools.prepare_metadata_for_build_wheel(metadata_directory=meta)
assert result is not None
dist = Distribution.at(str(result.metadata))
assert list(dist.entry_points) == [EntryPoint(name="demo_exe",
value="demo:a", group="console_scripts")]
assert dist.version == "1.0"
assert dist.metadata["Name"] == "demo"
values = [v for k, v in dist.metadata.items() if k == "Requires-Dist"]
# type: ignore[attr-defined]
# ignore because "PackageMetadata" has no attribute "items"
> assert sorted(values) == ["magic >3", "requests >2"]
E AssertionError: assert ['magic>3', 'requests>2'] == ['magic >3',
'requests >2']
E
E At index 0 diff: 'magic>3' != 'magic >3'
E Use -v to get more diff
tests/test_frontend_setuptools.py:76: AssertionError
=== short test summary info
FAILED
tests/test_frontend_setuptools.py::test_setuptools_prepare_metadata_for_build_wheel
= 1 failed, 58 passed in 5.63s =
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.12/build; python3.12 -m pytest tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12
returned exit code 13
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-09-19T22:17:52Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/799538/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/38989/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1082354: FTBFS ImportError: cannot import name 'hubs' from partially initialized module 'eventlet'
Control: notfound -1 aodh/18.0.0-2 Control: reassign -1 python3-eventlet Control: found -1 python3-eventlet/0.36.1-2 Control: affects -1 + src:aodh src:barbican src:keystone src:octavia src:openstack-trove src:python-ceilometermiddleware src:python-engineio src:python-futurist src:python-ironic-lib src:python-os-ken src:python-oslo.log src:python-oslo.messaging src:python-oslo.privsep src:python-oslo.service src:python-oslo.utils src:python-oslo.versionedobjects src:python-oslo.vmware src:python-os-vif src:python-os-win src:swift src:swift-bench src:vitrage src:watcher > I haven't investigated whether this is a failure in aodh or eventlet. > Please reassign if it's not aodh's problem. I've seen enough of these to reassign it. Stefano
Bug#1082394: FTBFS: debian/rules:68: *** Recursive variable 'PYBUILD_TEST_ARGS' references itself (eventually). Stop.
Source: satpy Version: 0.51.0-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, satpy failed to rebuild. --- [...] dpkg-buildpackage - Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot dpkg-buildpackage: info: source package satpy dpkg-buildpackage: info: source version 0.51.0-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Antonio Valentino dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 debian/rules clean dh clean --buildsystem=pybuild debian/rules:68: *** Recursive variable 'PYBUILD_TEST_ARGS' references itself (eventually). Stop. dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 Build finished at 2024-09-19T23:43:33Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/800854/ About the archive rebuild: The build was made on debusine.debian.net, on arm64 using sbuild. You can find the build task here: https://debusine.debian.net/work-request/39249/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1082392: python-ttn-client: FTBFS (requires Internet access)
Source: python-ttn-client
Version: 1.2.1-2
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, python-ttn-client failed to rebuild.
It appears to require Internet access to run the tests, which is against
Debian policy.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
---
[...]
* Building wheel...
Successfully built ttn_client-1.2.1-py3-none-any.whl
I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with
"installer" module
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd
/<>/.pybuild/cpython3_3.12_ttn-client/build; python3.12 -m pytest
--no-cov
= test session starts ==
platform linux -- Python 3.12.6, pytest-8.3.3, pluggy-1.5.0
rootdir: /<>/.pybuild/cpython3_3.12_ttn-client/build
configfile: pyproject.toml
plugins: typeguard-4.3.0, timeout-2.3.1, asyncio-0.20.3, cov-5.0.0
asyncio: mode=Mode.STRICT
collected 12 items
tests/parsers/test_default.py [ 33%]
tests/parsers/test_sensecap.py [ 66%]
tests/test_client.py .F..[100%]
=== FAILURES ===
__ test_connection_auth_error __
self =
req =
traces = []
timeout = ClientTimeout(total=600, connect=None, sock_read=None,
sock_connect=None, ceil_threshold=5)
async def _create_direct_connection(
self,
req: ClientRequest,
traces: List["Trace"],
timeout: "ClientTimeout",
*,
client_error: Type[Exception] = ClientConnectorError,
) -> Tuple[asyncio.Transport, ResponseHandler]:
sslcontext = await self._get_ssl_context(req)
fingerprint = self._get_fingerprint(req)
host = req.url.raw_host
assert host is not None
# Replace multiple trailing dots with a single one.
# A trailing dot is only present for fully-qualified domain names.
# See https://github.com/aio-libs/aiohttp/pull/7364.
if host.endswith(".."):
host = host.rstrip(".") + "."
port = req.port
assert port is not None
try:
# Cancelling this lookup should not cancel the underlying lookup
# or else the cancel event will get broadcast to all the waiters
# across all connections.
> hosts = await self._resolve_host(host, port, traces=traces)
/usr/lib/python3/dist-packages/aiohttp/connector.py:1301:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/aiohttp/connector.py:911: in _resolve_host
return await asyncio.shield(resolved_host_task)
/usr/lib/python3/dist-packages/aiohttp/connector.py:948: in
_resolve_host_with_throttle
addrs = await self._resolver.resolve(host, port, family=self._family)
/usr/lib/python3/dist-packages/aiohttp/resolver.py:37: in resolve
infos = await self._loop.getaddrinfo(
/usr/lib/python3.12/asyncio/base_events.py:901: in getaddrinfo
return await self.run_in_executor(
/usr/lib/python3.12/concurrent/futures/thread.py:58: in run
result = self.fn(*self.args, **self.kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
host = 'eu1.cloud.thethings.network', port = 443
family = , type =
proto = 0, flags =
def getaddrinfo(host, port, family=0, type=0, proto=0, flags=0):
"""Resolve host and port into list of address info entries.
Translate the host/port argument into a sequence of 5-tuples that
contain
all the necessary arguments for creating a socket connected to that
service.
host is a domain name, a string representation of an IPv4/v6 address or
None. port is a string service name such as 'http', a numeric port
number or
None. By passing None as the value of host and port, you can pass NULL
to
the underlying C API.
The family, type and proto arguments can be optionally specified in
order to
narrow the list of addresses returned. Passing zero as a value for each
of
these arguments selects the full range of results.
"""
# We override this function since we want to translate the numeric
family
# and socket type values to enum constants.
addrlist = []
> for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
E socket.gaierror: [Errno -3] Temporary failure in name resolution
/usr/lib/python3.12/socket.py:976: gaierror
The above exception was the direct cause of the following exception:
dummy_client =
@pytest.mark.asyncio
async def test_connection_auth_error(dummy_client):
"""Test that dummy credentials fail."""
Bug#1082393: FTBFS: TestBottleParser.test_parse_json_with_nonutf8_chars
Source: python-webargs
Version: 8.5.0-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, python-webargs failed to rebuild.
---
[...]
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_webargs/build;
python3.12 -m pytest -k 'not test_get_path_param and not
test_get_with_no_json_body and not test_post and not
test_missing_required_field_throws_422 and not test_required_field_provided and
not test_use_kwargs_with_error and not
test_user_validator_returns_422_by_default'
= test session starts ==
platform linux -- Python 3.12.6, pytest-8.3.3, pluggy-1.5.0
rootdir: /<>/.pybuild/cpython3_3.12_webargs/build
configfile: pyproject.toml
plugins: asyncio-0.20.3, typeguard-4.3.0
asyncio: mode=Mode.STRICT
collected 464 items / 7 deselected / 457 selected
tests/test_bottleparser.py .F...F..s [ 8%]
tests/test_core.py . [ 20%]
[ 36%]
.. [ 39%]
tests/test_djangoparser.py s [ 49%]
.[ 49%]
tests/test_falconparser.py .s... [ 59%]
.. [ 60%]
tests/test_flaskparser.py .. [ 70%]
.. [ 83%]
tests/test_pyramidparser.py ... [ 92%]
tests/test_tornadoparser.py .[100%]
=== FAILURES ===
_ TestBottleParser.test_parse_json_with_nonutf8_chars __
self =
testapp =
def test_parse_json_with_nonutf8_chars(self, testapp):
res = testapp.post(
"/echo_json",
b"\xfe",
headers={"Accept": "application/json", "Content-Type":
"application/json"},
expect_errors=True,
)
assert res.status_code == 400
> assert res.json == {"json": ["Invalid JSON body."]}
webargs/testing.py:162:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/webtest/response.py:470: in json
return self.json_body
/usr/lib/python3/dist-packages/webob/response.py:574: in _json_body__get
return json.loads(self.body.decode('UTF-8'))
/usr/lib/python3.12/json/__init__.py:346: in loads
return _default_decoder.decode(s)
/usr/lib/python3.12/json/decoder.py:337: in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , s = 'Invalid JSON'
idx = 0
def raw_decode(self, s, idx=0):
"""Decode a JSON document from ``s`` (a ``str`` beginning with
a JSON document) and return a 2-tuple of the Python
representation and the index in ``s`` where the document ended.
This can be used to decode a JSON document from a string that may
have extraneous data at the end.
"""
try:
obj, end = self.scan_once(s, idx)
except StopIteration as err:
> raise JSONDecodeError("Expecting value", s, err.value) from None
E json.decoder.JSONDecodeError: Expecting value: line 1 column 1
(char 0)
/usr/lib/python3.12/json/decoder.py:355: JSONDecodeError
__ TestBottleParser.test_invalid_json __
self =
testapp =
def test_invalid_json(self, testapp):
res = testapp.post(
"/echo_json",
'{"foo": "bar", }',
headers={"Accept": "application/json", "Content-Type":
"application/json"},
expect_errors=True,
)
assert res.status_code == 400
> assert res.json == {"json": ["Invalid JSON body."]}
webargs/testing.py:253:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/webtest/response.py:470: in json
return self.json_body
/usr/lib/python3/dist-packages/webob/response.py:574: in _json_body__get
return json.loads(self.body.decode('UTF-8'))
/usr/lib/python3.12/json/__init__.py:346: in loads
return _default_decoder.decode(s)
/usr/lib/python3.12/json/decoder.py:337: in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , s = 'Invalid JSON'
idx = 0
def raw_decode(self, s, idx=0):
"""Decode a JSON document from ``s`` (a ``str`` beginn
Bug#1082370: FTBFS: ModuleNotFoundError: No module named 'configobj'
Source: python-envisage
Version: 7.0.3-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, python-envisage failed to rebuild.
---
[...]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
xvfb-run -a dh_auto_test ## pybuild --test -i python${py3ver} -p "${py3ver}"
pybuild --test -i python{version} -p 3.12
I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_envisage/build;
python3.12 -m unittest discover -v
test_sys_path_inserted
(envisage.examples.tests.test__demo.TestDemoUtilities.test_sys_path_inserted)
... ok
test_info (envisage.examples.tests.test_etsdemo_info.TestETSDemoInfo.test_info)
... ok
test_file_resource
(envisage.resource.tests.test_resource_manager.ResourceManagerTestCase.test_file_resource)
file resource ... ok
test_http_resource
(envisage.resource.tests.test_resource_manager.ResourceManagerTestCase.test_http_resource)
http resource ... ok
test_no_such_file_resource
(envisage.resource.tests.test_resource_manager.ResourceManagerTestCase.test_no_such_file_resource)
no such file resource ... ok
test_no_such_http_resource
(envisage.resource.tests.test_resource_manager.ResourceManagerTestCase.test_no_such_http_resource)
no such http resource ... ok
test_no_such_package_resource
(envisage.resource.tests.test_resource_manager.ResourceManagerTestCase.test_no_such_package_resource)
no such package resource ... ok
test_package_resource
(envisage.resource.tests.test_resource_manager.ResourceManagerTestCase.test_package_resource)
package resource ... ok
test_package_resource_subdir
(envisage.resource.tests.test_resource_manager.ResourceManagerTestCase.test_package_resource_subdir)
package resource ... ok
test_unknown_protocol
(envisage.resource.tests.test_resource_manager.ResourceManagerTestCase.test_unknown_protocol)
unknown protocol ... ok
test_import (envisage.tests.test_api.TestApi.test_import) ... ok
test_add_extension_point_listener
(envisage.tests.test_application.ApplicationTestCase.test_add_extension_point_listener)
add extension point listener ... ok
test_add_plugin
(envisage.tests.test_application.ApplicationTestCase.test_add_plugin)
add plugin ... ok
test_extension_point
(envisage.tests.test_application.ApplicationTestCase.test_extension_point)
extension point ... ok
test_extension_point_resolution_occurs_after_plugin_start
(envisage.tests.test_application.ApplicationTestCase.test_extension_point_resolution_occurs_after_plugin_start)
... ok
test_get_plugin
(envisage.tests.test_application.ApplicationTestCase.test_get_plugin)
get plugin ... ok
test_home (envisage.tests.test_application.ApplicationTestCase.test_home)
home ... ok
test_no_plugins
(envisage.tests.test_application.ApplicationTestCase.test_no_plugins)
no plugins ... ERROR
test_remove_extension_point_listener
(envisage.tests.test_application.ApplicationTestCase.test_remove_extension_point_listener)
remove extension point listener ... ok
test_remove_plugin
(envisage.tests.test_application.ApplicationTestCase.test_remove_plugin)
remove plugin ... ok
test_set_plugin_manager_at_contruction_time
(envisage.tests.test_application.ApplicationTestCase.test_set_plugin_manager_at_contruction_time)
set plugin manager at construction time ... ok
test_start_and_stop_errors
(envisage.tests.test_application.ApplicationTestCase.test_start_and_stop_errors)
start and stop errors ... ok
test_veto_starting
(envisage.tests.test_application.ApplicationTestCase.test_veto_starting)
veto starting ... ok
test_veto_stopping
(envisage.tests.test_application.ApplicationTestCase.test_veto_stopping)
veto stopping ... ok
test_application_gets_propogated_to_plugin_managers
(envisage.tests.test_composite_plugin_manager.CompositePluginManagerTestCase.test_application_gets_propogated_to_plugin_managers)
... ok
test_correct_exception_propagated_from_plugin_manager
(envisage.tests.test_composite_plugin_manager.CompositePluginManagerTestCase.test_correct_exception_propagated_from_plugin_manager)
... ok
test_find_no_plugins_if_there_are_no_plugin_managers
(envisage.tests.test_composite_plugin_manager.CompositePluginManagerTestCase.test_find_no_plugins_if_there_are_no_plugin_managers)
... ok
test_find_no_plugins_if_there_are_no_plugins_in_plugin_managers
(envisage.tests.test_composite_plugin_manager.CompositePluginManagerTestCase.test_find_no_plugins_if_there_are_no_plugins_in_plugin_managers)
... ok
test_find_plugins_in_a_multiple_plugin_managers
(envisage.tests.test_composite_plugin_manager.CompositePluginManagerTestCase.test_find_plugins_in_a_multiple_plugin_managers)
... ok
test_find_plugins_in_a_single_plugin_manager
(envisage.tests.test_composite_plugin_manager.CompositePluginManagerTestCase.test_find_plugins_in_a_single_plugin_manager)
... ok
test_propogate_plugin_added_or_remove_events_from_plugin_managers
(envisage.tests.test_composite_plugin_manager.CompositePluginManagerTestCase.
Bug#1082369: FTBFS: ModuleNotFoundError: No module named 'setuptools.extern'
Source: python-daemon
Version: 3.0.1-1.1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, python-daemon failed to rebuild.
---
[...]
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 23, in
import version # noqa: E402
^^
File "/<>/version.py", line 39, in
import setuptools.extern.packaging.version
ModuleNotFoundError: No module named 'setuptools.extern'
E: pybuild pybuild:389: clean: plugin distutils failed with: exit code=1:
python3.12 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.12 returned exit
code 13
make: *** [debian/rules:21: clean] Error 25
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
Build finished at 2024-09-19T22:36:24Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/799793/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/39040/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1082368: FTBFS: TestIntegration.testIntegration: AssertionError: 1 != 0
Source: pychopper
Version: 2.7.10-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, pychopper failed to rebuild.
---
[...]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dh_auto_test -- --system=custom --test-args="export
PATH=/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/scripts:$PATH;
\
chmod +x
/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/scripts/pychopper;
PYTHONPATH={build_dir} {interpreter} -m pytest -v"
pybuild --test --test-pytest -i python{version} -p 3.12 --system=custom
"--test-args=export
PATH=/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;
chmod +x
/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/scripts/pychopper;
PYTHONPATH={build_dir} {interpreter} -m pytest -v"
I: pybuild pybuild:308: cp -av /<>/pychopper/tests/
/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/
'/<>/pychopper/tests/' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests'
'/<>/pychopper/tests/__init__.py' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/__init__.py'
'/<>/pychopper/tests/data' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/data'
'/<>/pychopper/tests/data/.gitignore' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/data/.gitignore'
'/<>/pychopper/tests/data/PCS111_umi_test_reads.fastq.gz' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/data/PCS111_umi_test_reads.fastq.gz'
'/<>/pychopper/tests/data/PCS111_umi_test_reads_expected.fastq' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/data/PCS111_umi_test_reads_expected.fastq'
'/<>/pychopper/tests/data/barcodes.fas' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/data/barcodes.fas'
'/<>/pychopper/tests/data/expected_output.fas' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/data/expected_output.fas'
'/<>/pychopper/tests/data/ref.fas.gz' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/data/ref.fas.gz'
'/<>/pychopper/tests/data/ref.fq.gz' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/data/ref.fq.gz'
'/<>/pychopper/tests/test_detector.py' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/test_detector.py'
'/<>/pychopper/tests/test_regression_simple.py' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/test_regression_simple.py'
'/<>/pychopper/tests/__pycache__' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/__pycache__'
'/<>/pychopper/tests/__pycache__/__init__.cpython-312.pyc' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/__pycache__/__init__.cpython-312.pyc'
'/<>/pychopper/tests/__pycache__/test_detector.cpython-312.pyc' ->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/__pycache__/test_detector.cpython-312.pyc'
'/<>/pychopper/tests/__pycache__/test_regression_simple.cpython-312.pyc'
->
'/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/tests/__pycache__/test_regression_simple.cpython-312.pyc'
I: pybuild base:311: export
PATH=/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;
chmod +x
/<>/.pybuild/cpython3_3.12_pychopper/build/pychopper/scripts/pychopper;
PYTHONPATH=/<>/.pybuild/cpython3_3.12_pychopper/build python3.12
-m pytest -v
= test session starts ==
platform linux -- Python 3.12.6, pytest-8.3.3, pluggy-1.5.0 --
/usr/bin/python3.12
cachedir: .pytest_cache
hypothesis profile 'default' ->
database=DirectoryBasedExampleDatabase(PosixPath('/<>/.hypothesis/examples'))
rootdir: /<>
configfile: pytest.ini
testpaths: pychopper
plugins: mock-3.14.0, openfiles-0.6.0, hypothesis-6.112.0, forked-1.6.0,
remotedata-0.4.1, typeguard-4.3.0, xdist-3.6.1, arraydiff-0.6.1,
doctestplus-1.2.1, timeout-2.3.1, xonsh-0.15.1, cov-5.0.0
collecting ... collected 4 items
pychopper/tests/test_detector.py::TestDetector::testPairAlign PASSED [ 25%]
pychopper/tests/test_detector.py::TestDetector::testScoreCutoff PASSED [ 50%]
pychopper/tests/test_regression_simple.py::TestIntegration::testIntegration
FAILED [ 75%]
pychopper/tests/test_regression_simple.py::TestIntegration::testIntegration_umi
FAILED [100%]
=== FAILURES ===
___ TestIntegration.testIntegration
self =
def testIntegration(self):
""" Integration test. """
base = path.dirname(__file__)
test_base = path.join(base, 'data')
barcodes = path.join(test_base, 'barcodes.fas')
input_fasta = path.join(test_base, 'ref.fq.gz')
output_fasta = path.join(test_base, 'test_output.fq.gz')
expected_output = path.joi
Bug#1082367: FTBFS: test_detect_lines_2dmode: AssertionError: Inconsistent results
Source: nitime Version: 0.10.2-2 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, nitime failed to rebuild. --- [...] dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build; python3.12 -m pytest = test session starts == platform linux -- Python 3.12.6, pytest-8.3.3, pluggy-1.5.0 rootdir: /<>/.pybuild/cpython3_3.12/build configfile: pyproject.toml plugins: typeguard-4.3.0 collected 124 items nitime/algorithms/tests/test_autoregressive.py . [ 4%] nitime/algorithms/tests/test_coherence.py ..s[ 16%] nitime/algorithms/tests/test_correlation.py .[ 16%] nitime/algorithms/tests/test_entropy.py .[ 20%] nitime/algorithms/tests/test_event_related.py . [ 21%] nitime/algorithms/tests/test_spectral.py [ 34%] nitime/analysis/tests/test_base.py . [ 35%] nitime/analysis/tests/test_coherence.py .. [ 40%] nitime/analysis/tests/test_correlation.py . [ 41%] nitime/analysis/tests/test_granger.py .. [ 42%] nitime/analysis/tests/test_snr.py . [ 43%] nitime/fmri/tests/test_io.py . [ 44%] nitime/tests/test_algorithms.py [ 50%] nitime/tests/test_analysis.py [ 57%] nitime/tests/test_descriptors.py . [ 58%] nitime/tests/test_lazy.py .. [ 59%] nitime/tests/test_timeseries.py [ 88%] nitime/tests/test_utils.py ..F [ 97%] nitime/tests/test_viz.py ... [100%] === FAILURES === ___ test_detect_lines_2dmode ___ def test_detect_lines_2dmode(): """ Test multi-sequence operation """ N = 1000 sig = np.cos( 2*np.pi*np.arange(N) * 20./N ) + np.random.randn(N) * .01 sig2d = np.row_stack( (sig, sig, sig) ) lines = utils.detect_lines(sig2d, (4, 8), low_bias=True, NFFT=2**12) npt.assert_(len(lines)==3, 'Detect lines failed multi-sequence mode') consistent1 = (lines[0][0] == lines[1][0]).all() and \ (lines[1][0] == lines[2][0]).all() consistent2 = (lines[0][1] == lines[1][1]).all() and \ (lines[1][1] == lines[2][1]).all() > npt.assert_(consistent1 and consistent2, 'Inconsistent results') E AssertionError: Inconsistent results nitime/tests/test_utils.py:304: AssertionError === warnings summary === nitime/algorithms/event_related.py:13 /<>/.pybuild/cpython3_3.12/build/nitime/algorithms/event_related.py:13: SyntaxWarning: invalid escape sequence '\h' """ nitime/analysis/tests/test_coherence.py::test_CoherenceAnalyzer nitime/analysis/tests/test_coherence.py::test_SparseCoherenceAnalyzer nitime/analysis/tests/test_coherence.py::test_SeedCoherenceAnalyzer /<>/.pybuild/cpython3_3.12/build/nitime/analysis/coherence.py:200: RuntimeWarning: invalid value encountered in divide delay[i, j] = this_phase / (2 * np.pi * self.frequencies) nitime/analysis/tests/test_coherence.py::test_CoherenceAnalyzer /<>/.pybuild/cpython3_3.12/build/nitime/analysis/coherence.py:200: RuntimeWarning: divide by zero encountered in divide delay[i, j] = this_phase / (2 * np.pi * self.frequencies) nitime/analysis/tests/test_coherence.py::test_CoherenceAnalyzer /<>/.pybuild/cpython3_3.12/build/nitime/algorithms/cohere.py:699: RuntimeWarning: divide by zero encountered in divide return (((np.abs(Rxy - Rxr * Rry)) ** 2) / nitime/analysis/tests/test_coherence.py::test_CoherenceAnalyzer /<>/.pybuild/cpython3_3.12/build/nitime/algorithms/cohere.py:699: RuntimeWarning: invalid value encountered in divide return (((np.abs(Rxy - Rxr * Rry)) ** 2) / nitime/analysis/tests/test_coherence.py::test_SparseCoherenceAnalyzer /<>/.pybuild/cpython3_3.12/build/nitime/analysis/coherence.py:523: RuntimeWarning: invalid value encountered in divide return self.relative_phases / (2 * np.pi * self.frequencies) nitime/analysis/tests/test_coherence.py::test_SeedCoherenceAnalyzer /<>/.pybuild/cpython3_3.12/build/nitime/analysis/coherence.py:730: RuntimeWarning: invalid value encountered in divide return self.relative_phases / (2 * np.pi * self.frequencies) nitime/analy
Bug#1082363: FTBFS: error: failed to select a version for the requirement `clap = "^4, <4.5"`
Source: lintian-brush
Version: 0.157
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, lintian-brush failed to rebuild.
---
[...]
running build_ext
running build_rust
error: failed to select a version for the requirement `clap = "^4, <4.5"`
candidate versions found which didn't match: 4.5.16
location searched: directory source `/usr/share/cargo/registry` (which is
replacing registry `crates-io`)
required by package `lintian-brush v0.157.0 (/<>/lintian-brush)`
perhaps a crate was updated and forgotten to be re-vendored?
error: `cargo metadata --manifest-path debianize/Cargo.toml --format-version 1`
failed with code 101
-- Output captured from stdout:
ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:389: build: plugin pyproject failed with: exit code=1:
python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir
/<>/.pybuild/cpython3_3.12
dh_auto_build: error: pybuild --build -i python{version} -p 3.12 returned exit
code 13
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-09-19T22:01:10Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/799351/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/38935/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1082364: FTBFS: Cannot find source file: searchengine.cpp
Source: morph-browser Version: 1.1.0+dfsg-2 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, morph-browser failed to rebuild. --- [...] dh_auto_configure cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb PKG_CONFIG=/usr/bin/pkg-config cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu .. -- The CXX compiler identification is GNU 14.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Gettext: /usr/bin/msgmerge (found version "0.22.5") -- Could NOT find Lcov (missing: LCOV_EXECUTABLE GENHTML_EXECUTABLE) -- Could NOT find gcovr (missing: GCOVR_EXECUTABLE) -- The C compiler identification is GNU 14.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1") -- Checking for module 'libapparmor' -- Found libapparmor, version 3.1.7 -- Configuring done (1.4s) CMake Error at tests/unittests/qml/CMakeLists.txt:34 (add_executable): Cannot find source file: /<>/bookmarks-model.cpp Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .ccm .cxxm .c++m .h .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc CMake Error at tests/unittests/search-engine/CMakeLists.txt:8 (add_executable): Cannot find source file: /<>/searchengine.cpp Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .ccm .cxxm .c++m .h .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc -- Generating done (0.2s) CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY FETCHCONTENT_FULLY_DISCONNECTED CMake Generate step failed. Build files cannot be regenerated correctly. cd obj-aarch64-linux-gnu && tail -v -n \+0 CMakeCache.txt ==> CMakeCache.txt <== # This is the CMakeCache file. # For build in directory: /<>/obj-aarch64-linux-gnu # It was generated by CMake: /usr/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. # EXTERNAL cache entries //Build as a click package CLICK_MODE:BOOL=OFF //Path to a program. CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //Choose the type of build, options are: None Debug Release RelWithDebInfo // MinSizeRel ... CMAKE_BUILD_TYPE:STRING=None //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ //A wrapper around 'ar' adding the appropriate '--plugin' option // for the GCC compiler CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-14 //A wrapper around 'ranlib' adding the appropriate '--plugin' option // for the GCC compiler CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-14 //Flags used by the CXX compiler during all build types. CMAKE_CXX_FLAGS:STRING=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 //Flags used by the CXX compiler during DEBUG builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the CXX compiler during MINSIZEREL builds. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the CXX compiler during NONE builds. CMAKE_CXX_FLAGS_NONE:STRING= //Flags used by the CXX compiler during RELEASE builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the CXX compiler during RELWITHDEBINFO builds. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc //A wrapper around 'ar' adding the appropriate '--plugin' option // for the GCC compiler CMAKE_C_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-14 //A wrapper around 'ranlib'
Bug#1081334: FTBFS in sbuild unshare backend
Hi Debian (2024.09.10_21:31:03_+0200) > Judging from the test, this may be specifically because of the unshare > build backend? They pass for me under Incus. Or because this was an IPv6-only buildd. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1082362: FTBFS in unstable: SEGV in test_gauss_nonsymmetric
Source: genx
Version: 3.6.23-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, genx failed to rebuild.
---
[...]
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build;
python3.12 -m pytest tests
= test session starts ==
platform linux -- Python 3.12.6, pytest-8.3.3, pluggy-1.5.0
rootdir: /<>/.pybuild/cpython3_3.12/build
configfile: pyproject.toml
plugins: typeguard-4.3.0
collected 40 items
tests/test_hdf5_interface.py . [ 2%]
tests/test_instrument.py . [ 25%]
tests/test_model.py [ 35%]
tests/test_numba_equivalency.py Fatal Python error: Segmentation fault
Current thread 0xab80c740 (most recent call first):
File
"/<>/.pybuild/cpython3_3.12/build/tests/test_numba_equivalency.py",
line 41 in test_gauss_nonsymmetric
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 351 in runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 174 in
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 103 in
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 120 in
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 513 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 242 in
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 341 in from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 241 in
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 132 in
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 113 in
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 103 in
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 120 in
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 513 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 362 in
pytest_runtestloopSegmentation fault
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=139: cd
/<>/.pybuild/cpython3_3.12/build; python3.12 -m pytest tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12
returned exit code 13
make: *** [debian/rules:11: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-09-19T21:56:34Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/799311/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/38916/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1082354: FTBFS ImportError: cannot import name 'hubs' from partially initialized module 'eventlet'
Source: aodh Version: 18.0.0-2 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, I haven't investigated whether this is a failure in aodh or eventlet. Please reassign if it's not aodh's problem. During a test rebuild, aodh failed to rebuild. --- [...] File "/usr/lib/python3/dist-packages/eventlet/convenience.py", line 4, in from eventlet import greenpool File "/usr/lib/python3/dist-packages/eventlet/greenpool.py", line 4, in from eventlet import queue File "/usr/lib/python3/dist-packages/eventlet/queue.py", line 48, in from eventlet.event import Event File "/usr/lib/python3/dist-packages/eventlet/event.py", line 1, in from eventlet import hubs ImportError: cannot import name 'hubs' from partially initialized module 'eventlet' (most likely due to a circular import) (/usr/lib/python3/dist-packages/eventlet/__init__.py) Failed to import test module: aodh.tests.unit.test_event Traceback (most recent call last): File "/usr/lib/python3.12/unittest/loader.py", line 396, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.12/unittest/loader.py", line 339, in _get_module_from_name __import__(name) File "/<>/aodh/tests/unit/test_event.py", line 20, in import oslo_messaging File "/usr/lib/python3/dist-packages/oslo_messaging/__init__.py", line 17, in from .notify import * File "/usr/lib/python3/dist-packages/oslo_messaging/notify/__init__.py", line 28, in from .listener import * File "/usr/lib/python3/dist-packages/oslo_messaging/notify/listener.py", line 140, in from oslo_messaging import server as msg_server File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 27, in from oslo_service import service File "/usr/lib/python3/dist-packages/oslo_service/service.py", line 35, in import eventlet File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line 6, in from eventlet import convenience File "/usr/lib/python3/dist-packages/eventlet/convenience.py", line 4, in from eventlet import greenpool File "/usr/lib/python3/dist-packages/eventlet/greenpool.py", line 4, in from eventlet import queue File "/usr/lib/python3/dist-packages/eventlet/queue.py", line 48, in from eventlet.event import Event File "/usr/lib/python3/dist-packages/eventlet/event.py", line 1, in from eventlet import hubs ImportError: cannot import name 'hubs' from partially initialized module 'eventlet' (most likely due to a circular import) (/usr/lib/python3/dist-packages/eventlet/__init__.py) Failed to import test module: aodh.tests.unit.test_messaging Traceback (most recent call last): File "/usr/lib/python3.12/unittest/loader.py", line 396, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.12/unittest/loader.py", line 339, in _get_module_from_name __import__(name) File "/<>/aodh/tests/unit/test_messaging.py", line 16, in import oslo_messaging.conffixture File "/usr/lib/python3/dist-packages/oslo_messaging/__init__.py", line 17, in from .notify import * File "/usr/lib/python3/dist-packages/oslo_messaging/notify/__init__.py", line 28, in from .listener import * File "/usr/lib/python3/dist-packages/oslo_messaging/notify/listener.py", line 140, in from oslo_messaging import server as msg_server File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 27, in from oslo_service import service File "/usr/lib/python3/dist-packages/oslo_service/service.py", line 35, in import eventlet File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line 6, in from eventlet import convenience File "/usr/lib/python3/dist-packages/eventlet/convenience.py", line 4, in from eventlet import greenpool File "/usr/lib/python3/dist-packages/eventlet/greenpool.py", line 4, in from eventlet import queue File "/usr/lib/python3/dist-packages/eventlet/queue.py", line 48, in from eventlet.event import Event File "/usr/lib/python3/dist-packages/eventlet/event.py", line 1, in from eventlet import hubs ImportError: cannot import name 'hubs' from partially initialized module 'eventlet' (most likely due to a circular import) (/usr/lib/python3/dist-packages/eventlet/__init__.py) Failed to import test module: aodh.tests.unit.test_notifier Traceback (most recent call last): File "/usr/lib/python3.12/unittest/loader.py", line 396, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.12/unittest/loader.py", line 339, in _get_module_from_name __import__(name) File "/<>/aodh/tests/unit/test_notifier.py", line 23, in import oslo_messaging File "/usr/lib/python3/dist-packages/oslo_messa
Bug#1082262: python-pyzipper FTBFS with Python 3.13
Source: python-pyzipper Version: 0.3.6-2 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: python3.13 This package failed build from source when test-built against a version of python3-defaults that includes 3.13 as a supported version. To reproduce this issue, build against python3-defaults (python3-all-dev etc.) from Debian experimental. What's new in Python 3.13: https://docs.python.org/3.13/whatsnew/3.13.html nntplib was removed in 3.13. Log snippet: dh_auto_test -O--buildsystem=pybuild I: pybuild pybuild:308: cp -r /<>/test /<>/.pybuild/cpython3_3.13_pyzipper/build I: pybuild base:311: cd /<>/.pybuild/cpython3_3.13_pyzipper/build; python3.13 -m pytest -v -p no:warnings -k 'not test_temp_dir__forked_child and not test_bad_use and not test_create_command and not test_extract_command and not test_test_command' = test session starts == platform linux -- Python 3.13.0rc2, pytest-8.3.3, pluggy-1.5.0 -- /usr/bin/python3.13 cachedir: .pytest_cache rootdir: /<> plugins: cov-5.0.0, flake8-1.1.1, typeguard-4.3.0 collecting ... collected 0 items / 5 errors ERRORS _ ERROR collecting .pybuild/cpython3_3.13_pyzipper/build/test/test_support.py __ ImportError while importing test module '/<>/.pybuild/cpython3_3.13_pyzipper/build/test/test_support.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.13/importlib/__init__.py:88: in import_module return _bootstrap._gcd_import(name[level:], package, level) test/test_support.py:15: in from test import support test/support/__init__.py:19: in import nntplib E ModuleNotFoundError: No module named 'nntplib' _ ERROR collecting .pybuild/cpython3_3.13_pyzipper/build/test/test_zipfile.py __ ImportError while importing test module '/<>/.pybuild/cpython3_3.13_pyzipper/build/test/test_zipfile.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.13/importlib/__init__.py:88: in import_module return _bootstrap._gcd_import(name[level:], package, level) test/test_zipfile.py:18: in from test.support import script_helper test/support/__init__.py:19: in import nntplib E ModuleNotFoundError: No module named 'nntplib' _ ERROR collecting .pybuild/cpython3_3.13_pyzipper/build/test/test_zipfile2.py _ ImportError while importing test module '/<>/.pybuild/cpython3_3.13_pyzipper/build/test/test_zipfile2.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.13/importlib/__init__.py:88: in import_module return _bootstrap._gcd_import(name[level:], package, level) test/test_zipfile2.py:21: in from test.support import script_helper test/support/__init__.py:19: in import nntplib E ModuleNotFoundError: No module named 'nntplib' _ ERROR collecting .pybuild/cpython3_3.13_pyzipper/build/test/test_zipfile64.py _ ImportError while importing test module '/<>/.pybuild/cpython3_3.13_pyzipper/build/test/test_zipfile64.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.13/importlib/__init__.py:88: in import_module return _bootstrap._gcd_import(name[level:], package, level) test/test_zipfile64.py:4: in from test import support test/support/__init__.py:19: in import nntplib E ModuleNotFoundError: No module named 'nntplib' _ ERROR collecting .pybuild/cpython3_3.13_pyzipper/build/test/test_zipfile_aes.py _ ImportError while importing test module '/<>/.pybuild/cpython3_3.13_pyzipper/build/test/test_zipfile_aes.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.13/importlib/__init__.py:88: in import_module return _bootstrap._gcd_import(name[level:], package, level) test/test_zipfile_aes.py:8: in from test.support import unlink test/support/__init__.py:19: in import nntplib E ModuleNotFoundError: No module named 'nntplib' === short test summary info ERROR test/test_support.py ERROR test/test_zipfile.py ERROR test/test_zipfile2.py ERROR test/test_zipfile64.py ERROR test/test_zipfile_aes.py !!! Interrupted: 5 errors during collection == 5 errors in 0.64s === E: pybuild pybuild:389: test: plugin distutils failed with: exit code=2: cd /<>/.pybuild/cpython3_3.13_pyzipper/build; python3.13 -m pytest -v -p no:warnings -k 'not test_temp_dir__forked_child and not test_bad_use and not test_create_command and not test_extract_command and not test_test_command' I: pybuild pybuild:308: cp -r /<>/test /<>/.pybuild/cpython3_3.12_pyzipper/build I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_pyzipper/build; python3.12 -m pytest -v -p no:warnings -k 'not test_temp_dir__forked_
Bug#1082131: uvloop FTBFS with Python 3.13
Source: uvloop Version: 0.20.0+ds1-1 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: python3.13 This package failed build from source when test-built against a version of python3-defaults that includes 3.13 as a supported version. To reproduce this issue, build against python3-defaults (python3-all-dev etc.) from Debian experimental. What's new in Python 3.13: https://docs.python.org/3.13/whatsnew/3.13.html Log snippet: = test session starts == platform linux -- Python 3.13.0rc2, pytest-8.3.3, pluggy-1.5.0 rootdir: /<>/.pybuild/cpython3_3.13_uvloop/build configfile: pyproject.toml plugins: typeguard-4.3.0 collected 351 items tests/test_aiohttp.py ...s tests/test_base.py .ss tests/test_context.py ..s..s.s.. tests/test_cython.py . tests/test_dealloc.py . tests/test_dns.py sss.ss. tests/test_executors.py tests/test_fs_event.py .. tests/test_process.py .. tests/test_process_spawning.py . tests/test_regr1.py . tests/test_runner.py .. tests/test_signals.py . tests/test_testbase.py ... tests/test_udp.py ..ss... tests/test_unix.py ..F... === FAILURES === ___ Test_AIO_Unix.test_create_unix_server_1 Traceback (most recent call last): File "/usr/lib/python3.13/unittest/case.py", line 58, in testPartExecutor yield File "/usr/lib/python3.13/unittest/case.py", line 651, in run self._callTestMethod(testMethod) File "/usr/lib/python3.13/unittest/case.py", line 606, in _callTestMethod if method() is not None: ~~^^ File "/<>/.pybuild/cpython3_3.13_uvloop/build/tests/test_unix.py", line 147, in test_create_unix_server_1 self.loop.run_until_complete(start_server()) File "/usr/lib/python3.13/asyncio/base_events.py", line 721, in run_until_complete return future.result() ~^^ File "/<>/.pybuild/cpython3_3.13_uvloop/build/tests/test_unix.py", line 100, in start_server self.assertTrue(os.path.exists(sock_name)) ~~~^^^ File "/usr/lib/python3.13/unittest/case.py", line 744, in assertTrue raise self.failureException(msg) AssertionError: False is not true === warnings summary === tests/test_aiohttp.py::Test_UV_AioHTTP::test_aiohttp_graceful_shutdown /<>/.pybuild/cpython3_3.13_uvloop/build/tests/test_aiohttp.py:85: NotAppKeyWarning: It is recommended to use web.AppKey instances for keys. https://docs.aiohttp.org/en/stable/web_advanced.html#application-s-config app['websockets'] = weakref.WeakSet() tests/test_aiohttp.py::Test_UV_AioHTTP::test_aiohttp_graceful_shutdown /usr/lib/python3/dist-packages/aiohttp/web_runner.py:95: DeprecationWarning: shutdown_timeout should be set on BaseRunner super().__init__( tests/test_executors.py::TestUVExecutors::test_executors_process_pool_01 tests/test_executors.py::TestAIOExecutors::test_executors_process_pool_01 tests/test_regr1.py::TestIssue39Regr::test_issue39_regression /usr/lib/python3.13/multiprocessing/popen_fork.py:67: DeprecationWarning: This process (pid=152) is multi-threaded, use of fork() may lead to deadlocks in the child. self.pid = os.fork() -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html === short test summary info FAILED tests/test_unix.py::Test_AIO_Unix::test_create_unix_server_1 - Asserti... === 1 failed, 337 passed, 13 skipped, 5 warnings in 62.53s (0:01:02) === E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.13_uvloop/build; python3.13 -m pytest -s tests --ignore=tests/test_pipes.py --ignore=tests/test_sourcecode.py --ignore=tests/test_sockets.py --ignore=tests/test_tcp.py --ignore=tests/test_libuv_api.py I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_uvloop/build; python3.12 -m pytest -s tests --ignore=tests/test_pipes.py --ignore=tests/test_sourcecode.py --ignore=tests/test_sockets.py --ignore=tests/test_tcp.py --ignore=tests/test_libuv_api.py = test session starts == platform linux -- Python 3.12.6, pytest-8.3.3, pluggy-1.5.0 rootdir: /<>/.pybuild/cpython3_3.12_uvloop/build configfile: pyproject.toml plugins: typeguard-4.3.0 collected 351 items tests/test_aiohttp.py ...s tests/test_base.py .ss tests/
Bug#1082130: sunpy FTBFS with Python 3.13
Source: sunpy Version: 6.0.2-1 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: python3.13 This package failed build from source when test-built against a version of python3-defaults that includes 3.13 as a supported version. To reproduce this issue, build against python3-defaults (python3-all-dev etc.) from Debian experimental. What's new in Python 3.13: https://docs.python.org/3.13/whatsnew/3.13.html Presumably -> will fix this. Log snippet: creating build/temp.linux-aarch64-cpython-313/sunpy/io/src creating build/temp.linux-aarch64-cpython-313/sunpy/io/src/ana aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.13 -c sunpy/io/src/ana/_pyana.c -o build/temp.linux-aarch64-cpython-313/sunpy/io/src/ana/_pyana.o -std=c99 -O3 -w sunpy/io/src/ana/_pyana.c: In function ‘pyana_fzwrite’: sunpy/io/src/ana/_pyana.c:286:19: error: implicit declaration of function ‘gmtime’ [-Wimplicit-function-declaration] 286 | tm_time = gmtime(&(tv_time->tv_sec)); | ^~ sunpy/io/src/ana/_pyana.c:22:1: note: ‘gmtime’ is defined in header ‘’; this is probably fixable by adding ‘#include ’ 21 | #include "anarw.h" +++ |+#include 22 | sunpy/io/src/ana/_pyana.c:286:17: error: assignment to ‘struct tm *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 286 | tm_time = gmtime(&(tv_time->tv_sec)); | ^ sunpy/io/src/ana/_pyana.c:290:20: error: invalid use of undefined type ‘struct tm’ 290 | tm_time->tm_hour, tm_time->tm_min, tm_time->tm_sec, (long) (tv_time->tv_usec/1000)); |^~ sunpy/io/src/ana/_pyana.c:290:38: error: invalid use of undefined type ‘struct tm’ 290 | tm_time->tm_hour, tm_time->tm_min, tm_time->tm_sec, (long) (tv_time->tv_usec/1000)); | ^~ sunpy/io/src/ana/_pyana.c:290:55: error: invalid use of undefined type ‘struct tm’ 290 | tm_time->tm_hour, tm_time->tm_min, tm_time->tm_sec, (long) (tv_time->tv_usec/1000)); | ^~ error: command '/usr/bin/aarch64-linux-gnu-gcc' failed with exit code 1 E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: /usr/bin/python3.13 setup.py build If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/776134/ This bug has been filed at "normal" severity, as we haven't started the transition to add 3.13 as a supported version, yet. This will be raised to RC as soon as that happens, hopefully well before trixie. Thanks, Stefano
Bug#1081549: marked as pending in twine
Control: tag -1 pending Hello, Bug #1081549 in twine reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/twine/-/commit/5afcaa8c9870a2301bf228dcfc78a367620aaf46 Patch: Restore support for pkginfo 1.11. * Patch: Restore support for pkginfo 1.11. * Revert the Build-Depends restriction on python-pkginfo. (Closes: #1081549) (this message was generated automatically) -- Greetings https://bugs.debian.org/1081549
Bug#1081687: Times out building on arm64
Source: cypari2 Version: 2.1.4-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, cypari2 failed to rebuild. --- [...] [7/7] Cythonizing cypari2/string_utils.pyx building 'cypari2.closure' extension creating build creating build/temp.linux-aarch64-cpython-312 creating build/temp.linux-aarch64-cpython-312/cypari2 aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Icypari2 -I/usr/lib/python3/dist-packages/cysignals -I/usr/include/python3.12 -c cypari2/closure.c -o build/temp.linux-aarch64-cpython-312/cypari2/closure.o aarch64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-aarch64-cpython-312/cypari2/closure.o -L/usr/lib/aarch64-linux-gnu -lgmp -lpari -o /<>/.pybuild/cpython3_3.12_cypari2/build/cypari2/closure.cpython-312-aarch64-linux-gnu.so building 'cypari2.convert' extension aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Icypari2 -I/usr/lib/python3/dist-packages/cysignals -I/usr/include/python3.12 -c cypari2/convert.c -o build/temp.linux-aarch64-cpython-312/cypari2/convert.o aarch64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-aarch64-cpython-312/cypari2/convert.o -L/usr/lib/aarch64-linux-gnu -lgmp -lpari -o /<>/.pybuild/cpython3_3.12_cypari2/build/cypari2/convert.cpython-312-aarch64-linux-gnu.so building 'cypari2.gen' extension aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Icypari2 -I/usr/lib/python3/dist-packages/cysignals -I/usr/include/python3.12 -c cypari2/gen.c -o build/temp.linux-aarch64-cpython-312/cypari2/gen.o cypari2/gen.c: In function ‘__pyx_pymod_exec_gen’: cypari2/gen.c:282008:30: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without 282008 | static CYTHON_SMALL_CODE int __pyx_pymod_exec_gen(PyObject *__pyx_pyinit_module) | ^~~~ aarch64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-aarch64-cpython-312/cypari2/gen.o -L/usr/lib/aarch64-linux-gnu -lgmp -lpari -o /<>/.pybuild/cpython3_3.12_cypari2/build/cypari2/gen.cpython-312-aarch64-linux-gnu.so building 'cypari2.handle_error' extension aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Icypari2 -I/usr/lib/python3/dist-packages/cysignals -I/usr/include/python3.12 -c cypari2/handle_error.c -o build/temp.linux-aarch64-cpython-312/cypari2/handle_error.o aarch64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-aarch64-cpython-312/cypari2/handle_error.o -L/usr/lib/aarch64-linux-gnu -lgmp -lpari -o /<>/.pybuild/cpython3_3.12_cypari2/build/cypari2/handle_error.cpython-312-aarch64-linux-gnu.so building 'cypari2.pari_instance' extension aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration -f
Bug#1081686: FTBFS with Python 3.12.6, gnutls 3.8.6-2
Source: pycurl Version: 7.45.3-2 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, Not entirely sure what's going on here, but during a test rebuild, pycurl failed to rebuild. --- [...] tests/multi_option_constants_test.py::MultiOptionConstantsTest::test_option_constant_on_curlmulti PASSED [ 30%] tests/multi_option_constants_test.py::MultiOptionConstantsTest::test_option_constant_on_pycurl PASSED [ 30%] tests/multi_option_constants_test.py::MultiOptionConstantsTest::test_pipe_constants PASSED [ 30%] tests/multi_socket_test.py::MultiSocketTest::test_multi_socket PASSED[ 30%] tests/multi_test.py::MultiTest::test_adding_closed_handle_close_then_remove PASSED [ 30%] tests/multi_test.py::MultiTest::test_adding_closed_handle_close_without_removing PASSED [ 31%] tests/multi_test.py::MultiTest::test_adding_closed_handle_remove_then_close PASSED [ 31%] tests/multi_test.py::MultiTest::test_keyword_arguments PASSED[ 31%] tests/multi_test.py::MultiTest::test_multi PASSED[ 31%] tests/multi_test.py::MultiTest::test_multi_close PASSED [ 32%] tests/multi_test.py::MultiTest::test_multi_close_twice PASSED[ 32%] tests/multi_test.py::MultiTest::test_multi_info_read Fatal Python error: Segmentation fault Thread 0xad884180 (most recent call first): File "/usr/lib/python3.12/socketserver.py", line 840 in write File "/usr/lib/python3.12/wsgiref/handlers.py", line 472 in _write File "/usr/lib/python3.12/wsgiref/handlers.py", line 271 in send_preamble File "/usr/lib/python3.12/wsgiref/handlers.py", line 351 in send_headers File "/usr/lib/python3.12/wsgiref/handlers.py", line 293 in write File "/usr/lib/python3.12/wsgiref/handlers.py", line 184 in finish_response File "/usr/lib/python3.12/wsgiref/handlers.py", line 138 in run File "/usr/lib/python3.12/wsgiref/simple_server.py", line 134 in handle File "/usr/lib/python3.12/socketserver.py", line 761 in __init__ File "/usr/lib/python3.12/socketserver.py", line 362 in finish_request File "/usr/lib/python3.12/socketserver.py", line 349 in process_request File "/usr/lib/python3.12/socketserver.py", line 318 in _handle_request_noblock File "/usr/lib/python3.12/socketserver.py", line 240 in serve_forever File "/<>/tests/runwsgi.py", line 28 in serve File "/<>/tests/runwsgi.py", line 14 in run File "/usr/lib/python3/dist-packages/bottle.py", line 3175 in run File "/<>/tests/runwsgi.py", line 69 in run File "/usr/lib/python3.12/threading.py", line 1075 in _bootstrap_inner File "/usr/lib/python3.12/threading.py", line 1032 in _bootstrap Thread 0xae994180 (most recent call first): File "/<>/tests/app.py", line 22 in short_wait File "/usr/lib/python3/dist-packages/bottle.py", line 1759 in wrapper File "/usr/lib/python3/dist-packages/bottle.py", line 876 in _handle File "/usr/lib/python3/dist-packages/bottle.py", line 968 in wsgi File "/usr/lib/python3/dist-packages/bottle.py", line 993 in __call__ File "/usr/lib/python3.12/wsgiref/handlers.py", line 137 in run File "/usr/lib/python3.12/wsgiref/simple_server.py", line 134 in handle File "/usr/lib/python3.12/socketserver.py", line 761 in __init__ File "/usr/lib/python3.12/socketserver.py", line 362 in finish_request File "/usr/lib/python3.12/socketserver.py", line 349 in process_request File "/usr/lib/python3.12/socketserver.py", line 318 in _handle_request_noblock File "/usr/lib/python3.12/socketserver.py", line 240 in serve_forever File "/<>/tests/runwsgi.py", line 28 in serve File "/<>/tests/runwsgi.py", line 14 in run File "/usr/lib/python3/dist-packages/bottle.py", line 3175 in run File "/<>/tests/runwsgi.py", line 69 in run File "/usr/lib/python3.12/threading.py", line 1075 in _bootstrap_inner File "/usr/lib/python3.12/threading.py", line 1032 in _bootstrap Thread 0xaf2a4180 (most recent call first): File "/usr/lib/python3.12/selectors.py", line 415 in select File "/usr/lib/python3.12/socketserver.py", line 235 in serve_forever File "/<>/tests/runwsgi.py", line 28 in serve File "/<>/tests/runwsgi.py", line 14 in run File "/usr/lib/python3/dist-packages/bottle.py", line 3175 in run File "/<>/tests/runwsgi.py", line 69 in run File "/usr/lib/python3.12/threading.py", line 1075 in _bootstrap_inner File "/usr/lib/python3.12/threading.py", line 1032 in _bootstrap Thread 0xafab4180 (most recent call first): File "/usr/lib/python3.12/selectors.py", line 415 in select File "/usr/lib/python3.12/socketserver.py", line 235 in serve_forever File "/<>/tests/runwsgi.py", line 28 in serve File "/<>/tests/runwsgi.py", line 46 in run File "/usr/lib/python3/dist-packages/bottle.py", line 3175 in run File "/<>/tests/runwsgi.py", line 69 in run File "/usr/lib/python3.12/threading.py", line 1075 in _bootstrap_inner File "/usr/lib/python3.12/threading.
Bug#1081664: FTBFS with GCC-14
Source: onnxruntime
Version: 1.16.3+dfsg-7
Severity: serious
Tags: ftbfs
Justification: FTBFS
This package failed build from source when test-built.
This was part of a Python 3.13 testing campaign, but it reproduces on
sid too.
Log snippet:
[ 10%] Building CXX object
CMakeFiles/onnxruntime_common.dir/<>/onnxruntime/core/platform/posix/ort_mutex.cc.o
/usr/bin/c++ -DCPUINFO_SUPPORTED_PLATFORM=1 -DDISABLE_ABSEIL -DEIGEN_MPL2_ONLY
-DEIGEN_USE_THREADS -DHAS_STRING_VIEW=1 -DNSYNC_ATOMIC_CPP11 -DONLY_C_LOCALE=1
-DORT_ENABLE_STREAM -DORT_NO_RTTI -DPLATFORM_POSIX -DUSE_XNNPACK=1
-D_GNU_SOURCE -I/<>/include/onnxruntime
-I/<>/include/onnxruntime/core/session
-I/<>/obj-aarch64-linux-gnu -I/<>/onnxruntime
-I/usr/include/eigen3 -I/usr/include/safeint -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2
-ffunction-sections -fdata-sections -DCPUINFO_SUPPORTED -O2 -g -DNDEBUG -fPIC
-fno-rtti -Wall -Wextra -Wno-deprecated-copy -Wno-nonnull-compare -Werror -MD
-MT
CMakeFiles/onnxruntime_common.dir/<>/onnxruntime/core/platform/posix/ort_mutex.cc.o
-MF
CMakeFiles/onnxruntime_common.dir/<>/onnxruntime/core/platform/posix/ort_mutex.cc.o.d
-o
CMakeFiles/onnxruntime_common.dir/<>/onnxruntime/core/platform/posix/ort_mutex.cc.o
-c /<>/onnxruntime/core/platform/posix/ort_mutex.cc
/<>/onnxruntime/core/providers/xnnpack/math/gemm.cc: In member
function ‘virtual onnxruntime::common::Status
onnxruntime::xnnpack::Gemm::PrePack(const onnxruntime::Tensor&, int,
onnxruntime::AllocatorPtr, bool&, onnxruntime::PrePackedWeights*)’:
/<>/onnxruntime/core/providers/xnnpack/math/gemm.cc:157:7: error:
cannot convert ‘xnn_operator**’ to ‘xnn_weights_cache_t’ {aka
‘xnn_weights_cache_provider*’}
157 | &p);
| ^~
| |
| xnn_operator**
In file included from
/<>/onnxruntime/core/providers/xnnpack/detail/utils.h:18,
from
/<>/onnxruntime/core/providers/xnnpack/math/gemm.h:9,
from
/<>/onnxruntime/core/providers/xnnpack/math/gemm.cc:4:
/usr/include/xnnpack.h:4312:23: note: initializing argument 11 of ‘xnn_status
xnn_create_fully_connected_nc_f32(size_t, size_t, size_t, size_t, const float*,
const float*, float, float, uint32_t, xnn_code_cache_t, xnn_weights_cache_t,
xnn_operator**)’
4312 | xnn_weights_cache_t weights_cache,
| ^
/<>/onnxruntime/core/providers/xnnpack/math/gemm.cc: In member
function ‘virtual onnxruntime::common::Status
onnxruntime::xnnpack::Gemm::Compute(onnxruntime::OpKernelContext*) const’:
/<>/onnxruntime/core/providers/xnnpack/math/gemm.cc:178:32: error:
invalid conversion from ‘int64_t’ {aka ‘long int’} to ‘const float*’
[-fpermissive]
178 | trans_A_ == CblasNoTrans ? M_ : K_, // Number of rows to multiply
| ~^
||
|int64_t {aka long int}
/<>/onnxruntime/core/providers/xnnpack/math/gemm.cc:179:21: error:
invalid conversion from ‘const float*’ to ‘float*’ [-fpermissive]
179 | A->Data(),
| ~~^~
| |
| const float*
/<>/onnxruntime/core/providers/xnnpack/math/gemm.cc:176:55: error:
too many arguments to function ‘xnn_status
xnn_setup_fully_connected_nc_f32(xnn_operator_t, const float*, float*)’
176 | xnn_status status = xnn_setup_fully_connected_nc_f32(
| ^
177 | op0_.get(),
| ~~~
178 | trans_A_ == CblasNoTrans ? M_ : K_, // Number of rows to multiply
| ~~
179 | A->Data(),
| ~
180 | Y->MutableData(),
|
181 | t_pool);
| ~~~
/usr/include/xnnpack.h:4320:17: note: declared here
4320 | enum xnn_status xnn_setup_fully_connected_nc_f32(
| ^~~~
[ 10%] Building CXX object
CMakeFiles/onnxruntime_mlas.dir/<>/onnxruntime/core/mlas/lib/halfgemm_kernel_neon.cpp.o
/usr/bin/c++ -DCPUINFO_SUPPORTED_PLATFORM=1 -DDISABLE_ABSEIL -DEIGEN_MPL2_ONLY
-DEIGEN_USE_THREADS -DNSYNC_ATOMIC_CPP11 -DORT_ENABLE_STREAM -DORT_NO_RTTI
-DPLATFORM_POSIX -DUSE_XNNPACK=1 -D_GNU_SOURCE
-I/<>/include/onnxruntime
-I/<>/include/onnxruntime/core/session
-I/<>/obj-aarch64-linux-gnu -I/<>/onnxruntime
-I/<>/onnxruntime/core/mlas/inc
-I/<>/onnxruntime/core/mlas/lib -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-mbranch-protection=standard -Wdate-time -D_FORTIFY_SOUR
Bug#1081631: FTBFS with Python 3.13
Source: pyzoltan Version: 1.0.1-9 Severity: serious Tags: ftbfs Justification: FTBFS This package failed build from source when test-built. The rebuild was part of a Python 3.13 rebuild, but it reproduces in a pristine sid environment. Log snippet: creating build/temp.linux-aarch64-cpython-313/pyzoltan/core aarch64-linux-gnu-g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/trilinos -I/<>/pyzoltan/czoltan -I/usr/lib/python3/dist-packages/cyarray -I/usr/lib/python3/dist-packages/mpi4py/include -I/usr/include/python3.13 -c pyzoltan/core/zoltan.cpp -o build/temp.linux-aarch64-cpython-313/pyzoltan/core/zoltan.o -I/usr/lib/aarch64-linux-gnu/openmpi/include -I/usr/lib/aarch64-linux-gnu/openmpi/include/openmpi In file included from /usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1929, from /usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12, from /usr/lib/python3/dist-packages/numpy/core/include/numpy/arrayobject.h:5, from pyzoltan/core/zoltan.cpp:1291: /usr/lib/python3/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp] 17 | #warning "Using deprecated NumPy API, disable it with " \ | ^~~ pyzoltan/core/zoltan.cpp:2287:3: error: ‘MPI_Session’ does not name a type 2287 | MPI_Session ob_mpi; | ^~~ error: command '/usr/bin/aarch64-linux-gnu-g++' failed with exit code 1 E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: /usr/bin/python3.13 setup.py build I: pybuild base:311: /usr/bin/python3 setup.py build -- Using Zoltan from: /usr/include/trilinos /usr/lib -- /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'setup_requres' warnings.warn(msg) running build running build_py creating /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan copying pyzoltan/api.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan copying pyzoltan/__init__.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan creating /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core copying pyzoltan/core/zoltan_utils.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core copying pyzoltan/core/__init__.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core creating /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/czoltan copying pyzoltan/czoltan/__init__.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/czoltan creating /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/tools copying pyzoltan/tools/__init__.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/tools copying pyzoltan/tools/run_parallel_script.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/tools creating /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core/tests copying pyzoltan/core/tests/zcomm.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core/tests copying pyzoltan/core/tests/__init__.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core/tests copying pyzoltan/core/tests/3d_partition.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core/tests copying pyzoltan/core/tests/test_zoltan.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core/tests copying pyzoltan/core/tests/geometric_partitioner.py -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core/tests running egg_info writing PyZoltan.egg-info/PKG-INFO writing dependency_links to PyZoltan.egg-info/dependency_links.txt writing requirements to PyZoltan.egg-info/requires.txt writing top-level names to PyZoltan.egg-info/top_level.txt reading manifest file 'PyZoltan.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'PyZoltan.egg-info/SOURCES.txt' copying pyzoltan/core/__init__.pxd -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core copying pyzoltan/core/msstdint.h -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core copying pyzoltan/core/zoltan.pxd -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core copying pyzoltan/core/zoltan_comm.pxd -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core copying pyzoltan/core/zoltan_dd.pxd -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/core copying pyzoltan/czoltan/__init__.pxd -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/czoltan copying pyzoltan/czoltan/czoltan.pxd -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/czoltan copying pyzoltan/czoltan/czoltan_comm.pxd -> /<>/.pybuild/cpython3_3.12_pyzoltan/build/pyzoltan/cz
Bug#1081543: FTBFS with PostgreSQL RC releases
Source: python-psycopg2cffi Version: 2.8.1-2 Severity: serious Tags: ftbfs Justification: FTBFS This package failed build from source in a rebuild. The rebuild was for Python 3.13, but the failure is unrelated to that. Log snippet: debian/rules override_dh_auto_install make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions pkgos-dh_auto_install --no-py2 --in-tmp + PKGOS_IN_TMP=no + echo WARNING: --no-py2 is deprecated and always on. WARNING: --no-py2 is deprecated and always on. + shift + PKGOS_IN_TMP=yes + shift + dpkg-parsechangelog -SSource + SRC_PKG_NAME=python-psycopg2cffi + echo python-psycopg2cffi + sed s/python-// + PY_MODULE_NAME=psycopg2cffi + py3versions -vr + PYTHON3S=3.13 3.12 + [ yes = yes ] + TARGET_DIR=tmp + pwd + python3.13 setup.py install --install-layout=deb --root /<>/debian/tmp /usr/lib/python3/dist-packages/setuptools/__init__.py:94: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. !! dist.fetch_build_eggs(dist.setup_requires) /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) Error: could not determine PostgreSQL version from '17rc1'make[1]: *** [debian/rules:18: override_dh_auto_install] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 Build finished at 2024-09-12T14:40:27Z If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/705643/ This bug has been filed at "normal" severity, as we haven't started the transition to add 3.13 as a supported version, yet. This will be raised to RC as soon as that happens, hopefully well before trixie. Thanks, Stefano
Bug#1081539: FTBFS with Python 3.12.6
Source: python-pyeclib
Version: 1.6.1-2
Severity: serious
Tags: ftbfs
Justification: FTBFS
This package failed build from source during a rebuild. Interestingly,
this was a build with Python 3.13 available, and the 3.13 part passed
tests, but 3.12.6 triggered a test failure. I can reproduce this in sid
without Python 3.13.
Log snippet:
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
30 passed, 4 skipped, 1 deselected, 3859 warnings in 74.88s (0:01:14) =
I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_py/build;
python3.12 -m pytest -v -k 'not test_get_metadata_memory_usage'
= test session starts ==
platform linux -- Python 3.12.6, pytest-8.3.2, pluggy-1.5.0 --
/usr/bin/python3.12
cachedir: .pytest_cache
rootdir: /<>
plugins: typeguard-4.3.0
collecting ... collected 35 items / 1 deselected / 34 selected
test/test_pyeclib_api.py::TestNullDriver::test_null_driver PASSED[ 2%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_attribute_error_in_the_error_handling
PASSED [ 5%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_decode_reconstruct_with_fragment_iterator
PASSED [ 8%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_encode_invalid_params PASSED
[ 11%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_get_metadata_formatted PASSED
[ 14%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_get_segment_byterange_info
PASSED [ 17%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_get_segment_info PASSED [ 20%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_get_segment_info_memory_usage
PASSED [ 23%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_greedy_decode_reconstruct_combination
PASSED [ 26%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_import_error_in_the_error_handling
PASSED [ 29%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_invalid_km_args PASSED [ 32%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_liberasurecode_insufficient_frags_error
PASSED [ 35%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_min_parity_fragments_needed
PASSED [ 38%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_missing_required_args PASSED
[ 41%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_pyeclib_driver_repr_expression
PASSED [ 44%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_rs PASSED [ 47%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_small_encode PASSED[ 50%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_valid_algo PASSED [ 52%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_valid_ec_types PASSED [ 55%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_verify_fragment_inline_chksum_fail
PASSED [ 58%]
test/test_pyeclib_api.py::TestPyECLibDriver::test_verify_fragment_inline_chksum_succeed
PASSED [ 61%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_flat_xor_hd_3_available
PASSED [ 64%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_flat_xor_hd_4_available
PASSED [ 67%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_isa_l_rs_cauchy_available
PASSED [ 70%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_isa_l_rs_vand_available
PASSED [ 73%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_jerasure_rs_cauchy_available
PASSED [ 76%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_jerasure_rs_vand_available
PASSED [ 79%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_liberasurecode_rs_vand_available
PASSED [ 82%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_libphazr_available SKIPPED
[ 85%]
test/test_pyeclib_api.py::TestBackendsEnabled::test_shss_available SKIPPED [
88%]
test/test_pyeclib_c.py::TestPyECLib::test_codes FAILED [ 91%]
test/test_pyeclib_c.py::TestPyECLib::test_libphazr SKIPPED (libphazr...) [ 94%]
test/test_pyeclib_c.py::TestPyECLib::test_shss SKIPPED (shss backend...) [ 97%]
test/test_pyeclib_c.py::TestPyECLib::test_xor_code PASSED[100%]
=== FAILURES ===
TestPyECLib.test_codes
self =
def test_codes(self):
for ec_type in self.iter_available_types(self.rs_types):
for i in range(len(self.num_datas)):
success = self._test_get_required_fragments(
self.num_datas[i], self.num_parities[i], ec_type)
self.assertTrue(success)
for i in range(len(self.num_datas)):
for size_str in self.sizes:
avg_time = self.time_encode(
self.num_datas[i], self.num_parities[i], ec_type.value,
self.num_parities[i] + 1, size_str, self.iterations)
print("Encode (%s): %s" %
(size_str, self.get_throughput(avg_time, size_str)))
for i in range(len(self.num_datas)):
for size_str in self.sizes:
Bug#1080584: FTBFS with GCC-14
This got reopened, the real bug here is:
make[6]: Entering directory '/<>/modules/python'
/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../../include/lib -I../../include -I../../include -I../../grecs/include
-I../../grecs/wordsplit -I../../grecs/include -I/usr/include/python3.12
-I/usr/include/python3.12 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -mbranch-protection=standard -c -o python.lo python.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../include/lib -I../../include
-I../../include -I../../grecs/include -I../../grecs/wordsplit
-I../../grecs/include -I/usr/include/python3.12 -I/usr/include/python3.12
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-mbranch-protection=standard -c python.c -fPIC -DPIC -o .libs/python.o
In file included from /usr/include/python3.12/Python.h:44,
from python.c:19:
/usr/include/python3.12/object.h:142:9: error: initialization of 'long int'
from 'PyTypeObject *' {aka 'struct _typeobject *'} makes integer from pointer
without a cast [-Wint-conversion]
142 | (type) \
| ^
python.c:97:5: note: in expansion of macro 'PyObject_HEAD_INIT'
97 | PyObject_HEAD_INIT(&PyType_Type)
| ^~
/usr/include/python3.12/object.h:142:9: note: (near initialization for
'PySelectionKeyType.ob_base.ob_size')
142 | (type) \
| ^
python.c:97:5: note: in expansion of macro 'PyObject_HEAD_INIT'
97 | PyObject_HEAD_INIT(&PyType_Type)
| ^~
/usr/include/python3.12/object.h:142:9: error: initialization of 'long int'
from 'PyTypeObject *' {aka 'struct _typeobject *'} makes integer from pointer
without a cast [-Wint-conversion]
142 | (type) \
| ^
python.c:182:5: note: in expansion of macro 'PyObject_HEAD_INIT'
182 | PyObject_HEAD_INIT(&PyType_Type)
| ^~
/usr/include/python3.12/object.h:142:9: note: (near initialization for
'PyStrategyType.ob_base.ob_size')
142 | (type) \
| ^
python.c:182:5: note: in expansion of macro 'PyObject_HEAD_INIT'
182 | PyObject_HEAD_INIT(&PyType_Type)
| ^~
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
Bug#1081341: FTBFS with Python 3.12 AttributeError: module 'configparser' has no attribute 'SafeConfigParser'
Source: igdiscover
Version: 0.11-4
Severity: serious
Tags: ftbfs sid trixie
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Dear maintainer,
During a test rebuild, igdiscover failed to rebuild.
https://docs.python.org/3/whatsnew/3.12.html#configparser
---
[...]
dh clean --with python3,sphinxdoc --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
pybuild --clean -i python{version} -p 3.12
I: pybuild base:311: python3.12 setup.py clean
/<>/versioneer.py:485: SyntaxWarning: invalid escape sequence '\s'
LONG_VERSION_PY['git'] = '''
Traceback (most recent call last):
File "/<>/setup.py", line 15, in
version = versioneer.get_version(),
File "/<>/versioneer.py", line 1473, in get_version
return get_versions()["version"]
^^
File "/<>/versioneer.py", line 1406, in get_versions
cfg = get_config_from_root(root)
^^
File "/<>/versioneer.py", line 412, in get_config_from_root
parser = configparser.SafeConfigParser()
^
AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did
you mean: 'RawConfigParser'?
E: pybuild pybuild:389: clean: plugin distutils failed with: exit code=1:
python3.12 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.12 returned exit
code 13
make[1]: *** [debian/rules:21: override_dh_auto_clean] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit
status 2
Build finished at 2024-09-07T16:09:17Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/611761/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/20684/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1081342: FTBFS: gpg.errors.GPGMEError: gpgme_op_encrypt_sign: GnuPG: No agent running
Source: impass
Version: 0.13.1-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, impass failed to rebuild.
---
[...]
func(args)
File "/<>/impass/__main__.py", line 261, in add
db.save()
File "/<>/impass/db.py", line 249, in save
encdata = self._encrypt_db(cleardata, keyid)
^^
File "/<>/impass/db.py", line 139, in _encrypt_db
encdata, _, _ = self._gpg.encrypt(
^^
File "/usr/lib/python3/dist-packages/gpg/core.py", line 339, in encrypt
raise e
File "/usr/lib/python3/dist-packages/gpg/core.py", line 316, in encrypt
self.op_encrypt_sign(recipients, flags, plaintext, ciphertext)
File "/usr/lib/python3/dist-packages/gpg/core.py", line 171, in wrapper
return _funcwrap(self, *args)
^^
File "/usr/lib/python3/dist-packages/gpg/core.py", line 147, in _funcwrap
return errorcheck(result, name)
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: gpgme_op_encrypt_sign: GnuPG: No agent running
FAIL add second entry
impass add 'baz asdf Dokw okb 32438uoijdf'
Auto-generating password...
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/<>/impass/__main__.py", line 771, in
main()
File "/<>/impass/__main__.py", line 767, in main
func(args)
File "/<>/impass/__main__.py", line 261, in add
db.save()
File "/<>/impass/db.py", line 249, in save
encdata = self._encrypt_db(cleardata, keyid)
^^
File "/<>/impass/db.py", line 139, in _encrypt_db
encdata, _, _ = self._gpg.encrypt(
^^
File "/usr/lib/python3/dist-packages/gpg/core.py", line 339, in encrypt
raise e
File "/usr/lib/python3/dist-packages/gpg/core.py", line 316, in encrypt
self.op_encrypt_sign(recipients, flags, plaintext, ciphertext)
File "/usr/lib/python3/dist-packages/gpg/core.py", line 171, in wrapper
return _funcwrap(self, *args)
^^
File "/usr/lib/python3/dist-packages/gpg/core.py", line 147, in _funcwrap
return errorcheck(result, name)
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: gpgme_op_encrypt_sign: GnuPG: No agent running
FAIL 2
add existing context impass add foo@bar
Auto-generating password...
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/<>/impass/__main__.py", line 771, in
main()
File "/<>/impass/__main__.py", line 767, in main
func(args)
File "/<>/impass/__main__.py", line 261, in add
db.save()
File "/<>/impass/db.py", line 249, in save
encdata = self._encrypt_db(cleardata, keyid)
^^
File "/<>/impass/db.py", line 139, in _encrypt_db
encdata, _, _ = self._gpg.encrypt(
^^
File "/usr/lib/python3/dist-packages/gpg/core.py", line 339, in encrypt
raise e
File "/usr/lib/python3/dist-packages/gpg/core.py", line 316, in encrypt
self.op_encrypt_sign(recipients, flags, plaintext, ciphertext)
File "/usr/lib/python3/dist-packages/gpg/core.py", line 171, in wrapper
return _funcwrap(self, *args)
^^
File "/usr/lib/python3/dist-packages/gpg/core.py", line 147, in _funcwrap
return errorcheck(result, name)
File "/usr/lib/python3/dist-packages/gpg/errors.py", line 129, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: gpgme_op_encrypt_sign: GnuPG: No agent running
FAIL dump all entries
--- cli.5.expected 2024-09-07 16:10:16.33600 +
+++ cli.5.output2024-09-07 16:10:16.33200 +
@@ -1,8 +1,3 @@
-{
- "baz asdf Dokw okb 32438uoijdf": {
-FOO
- },
- "foo@bar": {
-FOO
- }
-}
+Impass database does not exist.
+To add an entry to the database use 'impass add'.
+See 'impass help' for more information.
FAIL dump search 0
--- cli.6.expected 2024-09-07 16:10:16.51200 +
+++ cli.6.output2024-09-07 16:10:16.50800 +
@@ -1,5 +1,3 @@
-{
- "foo@bar": {
-FOO
- }
-}
+Impass database does not exist.
+To add an entry to the database use 'impass add'.
+See 'impass help' for more information.
FAIL dump search 1
--- cli.7.expected 2024-0
Bug#1081340: FTBFS with python3-attr 24: ImportError: cannot import name 'provides' from 'attr.validators'
Source: gnome-keysign Version: 1.3.0-3 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild, gnome-keysign failed to rebuild. https://www.attrs.org/en/stable/changelog.html#id2 --- [...] debian/rules override_dh_auto_test make[1]: Entering directory '/<>' xvfb-run -a python3 -m pytest = test session starts == platform linux -- Python 3.12.5, pytest-8.3.2, pluggy-1.5.0 rootdir: /<> plugins: typeguard-4.3.0, twisted-1.14.1 collected 34 items / 3 errors ERRORS ___ ERROR collecting tests/test_bluetooth.py ___ ImportError while importing test module '/<>/tests/test_bluetooth.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.12/importlib/__init__.py:90: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_bluetooth.py:21: in from keysign.util import mac_generate keysign/util.py:43: in from wormhole._wordlist import PGPWordList /usr/lib/python3/dist-packages/wormhole/__init__.py:2: in from .wormhole import create /usr/lib/python3/dist-packages/wormhole/wormhole.py:11: in from ._boss import Boss /usr/lib/python3/dist-packages/wormhole/_boss.py:4: in from attr.validators import instance_of, optional, provides E ImportError: cannot import name 'provides' from 'attr.validators' (/usr/lib/python3/dist-packages/attr/validators.py) ERROR collecting tests/test_latin1.py _ ImportError while importing test module '/<>/tests/test_latin1.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.12/importlib/__init__.py:90: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_latin1.py:12: in from keysign.KeyPresent import KeyPresentWidget keysign/KeyPresent.py:43: in from .util import format_fingerprint keysign/util.py:43: in from wormhole._wordlist import PGPWordList /usr/lib/python3/dist-packages/wormhole/__init__.py:2: in from .wormhole import create /usr/lib/python3/dist-packages/wormhole/wormhole.py:11: in from ._boss import Boss /usr/lib/python3/dist-packages/wormhole/_boss.py:4: in from attr.validators import instance_of, optional, provides E ImportError: cannot import name 'provides' from 'attr.validators' (/usr/lib/python3/dist-packages/attr/validators.py) ___ ERROR collecting tests/test_wormhole.py ImportError while importing test module '/<>/tests/test_wormhole.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.12/importlib/__init__.py:90: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_wormhole.py:32: in from keysign.offer import Offer keysign/offer.py:4: in from .wormholeoffer import WormholeOffer keysign/wormholeoffer.py:26: in from wormhole.cli.public_relay import RENDEZVOUS_RELAY /usr/lib/python3/dist-packages/wormhole/__init__.py:2: in from .wormhole import create /usr/lib/python3/dist-packages/wormhole/wormhole.py:11: in from ._boss import Boss /usr/lib/python3/dist-packages/wormhole/_boss.py:4: in from attr.validators import instance_of, optional, provides E ImportError: cannot import name 'provides' from 'attr.validators' (/usr/lib/python3/dist-packages/attr/validators.py) === warnings summary === keysign/QRCode.py:197 /<>/keysign/QRCode.py:197: PyGIDeprecationWarning: GObject.property is deprecated; use GObject.Property instead data = GObject.property(getter=get_data, setter=set_data) -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html === short test summary info ERROR tests/test_bluetooth.py ERROR tests/test_latin1.py ERROR tests/test_wormhole.py !!! Interrupted: 3 errors during collection = 1 warning, 3 errors in 0.61s = make[1]: *** [debian/rules:38: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:20: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-09-07T15:46:40Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/611519/ About the archive rebuild: The build was made
Bug#1081334: FTBFS in sbuild unshare backend
Source: async-upnp-client
Version: 0.40.0-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, async-upnp-client failed to rebuild.
Judging from the test, this may be specifically because of the unshare
build backend? They pass for me under Incus.
Probably these ENODEV errors could be caught and turned into test skips.
---
[...]
type=socket.SOCK_DGRAM,
proto=socket.IPPROTO_UDP,
)[0]
source_ip, source_port = ip_port_from_address_tuple(source)
source_info = socket.getaddrinfo(
str(source_ip), source_port, type=socket.SOCK_DGRAM,
proto=socket.IPPROTO_UDP
)[0]
_LOGGER.debug("Creating socket, source: %s, target: %s", source_info,
target_info)
# create socket
sock = socket.socket(source_info[0], source_info[1])
# set options
sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
try:
sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEPORT, 1)
except AttributeError:
pass
sock.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
# multicast
if target_ip.is_multicast:
if source_info[0] == socket.AF_INET6:
sock.setsockopt(socket.IPPROTO_IPV6,
socket.IPV6_MULTICAST_HOPS, 2)
addr = cast(AddressTupleV6Type, source_info[4])
if addr[3]:
mreq = target_ip.packed + addr[3].to_bytes(4, sys.byteorder)
sock.setsockopt(socket.IPPROTO_IPV6,
socket.IPV6_JOIN_GROUP, mreq)
sock.setsockopt(socket.IPPROTO_IPV6,
socket.IPV6_MULTICAST_IF, addr[3])
else:
_LOGGER.debug("Skipping setting multicast interface")
else:
sock.setsockopt(socket.IPPROTO_IP, socket.IP_MULTICAST_IF,
source_ip.packed)
sock.setsockopt(socket.IPPROTO_IP, socket.IP_MULTICAST_TTL, 2)
> sock.setsockopt(
socket.IPPROTO_IP,
socket.IP_ADD_MEMBERSHIP,
target_ip.packed + source_ip.packed,
)
E OSError: [Errno 19] No such device
async_upnp_client/ssdp.py:491: OSError
_ test_see_search_device_ipv4_and_ipv6 _
@pytest.mark.asyncio
async def test_see_search_device_ipv4_and_ipv6() -> None:
"""Test seeing the same device via IPv4, then via IPv6."""
# pylint: disable=protected-access
async_callback = AsyncMock()
listener = SsdpListener(async_callback=async_callback)
> await listener.async_start()
tests/test_ssdp_listener.py:686:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
async_upnp_client/ssdp_listener.py:520: in async_start
await self._advertisement_listener.async_start()
async_upnp_client/advertisement.py:118: in async_start
sock, _source, _target = get_ssdp_socket(self.source, self.target)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
source = ('0.0.0.0', 0), target = ('239.255.255.250', 1900)
def get_ssdp_socket(
source: AddressTupleVXType,
target: AddressTupleVXType,
) -> Tuple[socket.socket, AddressTupleVXType, AddressTupleVXType]:
"""Create a socket to listen on."""
# Ensure a proper IPv6 source/target.
if is_ipv6_address(source):
source = cast(AddressTupleV6Type, source)
if not source[3]:
raise UpnpError(f"Source missing scope_id, source: {source}")
if is_ipv6_address(target):
target = cast(AddressTupleV6Type, target)
if not target[3]:
raise UpnpError(f"Target missing scope_id, target: {target}")
target_ip, target_port = ip_port_from_address_tuple(target)
target_info = socket.getaddrinfo(
str(target_ip),
target_port,
type=socket.SOCK_DGRAM,
proto=socket.IPPROTO_UDP,
)[0]
source_ip, source_port = ip_port_from_address_tuple(source)
source_info = socket.getaddrinfo(
str(source_ip), source_port, type=socket.SOCK_DGRAM,
proto=socket.IPPROTO_UDP
)[0]
_LOGGER.debug("Creating socket, source: %s, target: %s", source_info,
target_info)
# create socket
sock = socket.socket(source_info[0], source_info[1])
# set options
sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
try:
sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEPORT, 1)
except AttributeError:
pass
sock.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
# multicast
if target_ip.is_multicast:
if source_info[0] == socket.AF_INET6:
sock.setsocko
Bug#1081301: FTBFS with GCC-14
Source: aggdraw
Version: 1.3.18-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, aggdraw failed to rebuild.
---
[...]
creating build/temp.linux-aarch64-cpython-312/agg2/src
aarch64-linux-gnu-g++ -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -mbranch-protection=standard -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -DVERSION=1.3.18 -DHAVE_FREETYPE2 -Iagg2/include
-Iagg2/font_freetype -I/usr/include -I/usr/include/freetype
-I/usr/include/freetype2 -I/usr/include/python3.12 -c
agg2/font_freetype/agg_font_freetype.cpp -o
build/temp.linux-aarch64-cpython-312/agg2/font_freetype/agg_font_freetype.o
agg2/font_freetype/agg_font_freetype.cpp: In member function ‘void
agg::font_engine_freetype_base::update_signature()’:
agg2/font_freetype/agg_font_freetype.cpp:766:44: warning: format ‘%d’ expects
argument of type ‘int’, but argument 10 has type ‘FT_Fixed’ {aka ‘long int’}
[-Wformat=]
766 | "%s,%u,%d,%d,%d:%dx%d,%d,%d,%d,%d,%d,%d,%08X",
| ~^
||
|int
| %ld
..
774 | m_matrix.xx,
| ~~~
| |
| FT_Fixed {aka long int}
agg2/font_freetype/agg_font_freetype.cpp:766:47: warning: format ‘%d’ expects
argument of type ‘int’, but argument 11 has type ‘FT_Fixed’ {aka ‘long int’}
[-Wformat=]
766 | "%s,%u,%d,%d,%d:%dx%d,%d,%d,%d,%d,%d,%d,%08X",
| ~^
| |
| int
| %ld
..
775 | m_matrix.xy,
| ~~~
| |
| FT_Fixed {aka long int}
agg2/font_freetype/agg_font_freetype.cpp:766:50: warning: format ‘%d’ expects
argument of type ‘int’, but argument 12 has type ‘FT_Fixed’ {aka ‘long int’}
[-Wformat=]
766 | "%s,%u,%d,%d,%d:%dx%d,%d,%d,%d,%d,%d,%d,%08X",
| ~^
| |
| int
| %ld
..
776 | m_matrix.yx,
| ~~~
| |
| FT_Fixed {aka long int}
agg2/font_freetype/agg_font_freetype.cpp:766:53: warning: format ‘%d’ expects
argument of type ‘int’, but argument 13 has type ‘FT_Fixed’ {aka ‘long int’}
[-Wformat=]
766 | "%s,%u,%d,%d,%d:%dx%d,%d,%d,%d,%d,%d,%d,%08X",
|~^
| |
| int
|%ld
..
777 | m_matrix.yy,
| ~~~
| |
| FT_Fixed {aka long int}
agg2/font_freetype/agg_font_freetype.cpp: In instantiation of ‘bool
agg::decompose_ft_outline(const FT_Outline&, bool, PathStorage&, ConvCoord)
[with PathStorage = path_storage_integer; ConvCoord = int (*)(int);
FT_Outline = FT_Outline_]’:
agg2/font_freetype/agg_font_freetype.cpp:883:48: required from here
883 |
if(decompose_ft_outline(m_cur_face->glyph->outline,
|
^~~~
884 | flip,
| ~
885 | m_path32,
| ~
886 | conv_coord_none))
|
agg2/font_freetype/agg_font_freetype.cpp:174:35: error: invalid conversion from
‘unsigned char*’ to ‘char*’ [-fpermissive]
174 | tags = outline.tags + first;
| ~~^~~
| |
| unsigned char*
agg2/font_freetype/agg_font_freetype.cpp: In instantiation of ‘bool
agg::decompose_ft_outline(const FT_Outline&, bool, PathStorage&, ConvCoord)
[
Bug#1080213: marked as pending in distro-info
Control: tag -1 pending Hello, Bug #1080213 in distro-info reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/distro-info/-/commit/732f4247f8172fd3c80168e01ae03526373bd0de Python: Stop using setup.py test. (Closes: #1080213) (this message was generated automatically) -- Greetings https://bugs.debian.org/1080213
Bug#1080287: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: straight.plugin
Version: 1.4.1-5
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72, straight.plugin
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
build succeeded, 5 warnings.
The manual pages are in _build/man.
Build finished. The manual pages are in _build/man.
make[2]: Leaving directory '/<>/docs'
make[1]: Leaving directory '/<>'
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom \
PYBUILD_TEST_ARGS="{interpreter} setup.py test" \
dh_auto_test
I: pybuild base:311: python3.12 setup.py test
/usr/lib/python3/dist-packages/setuptools/dist.py:653:
SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated.
!!
Please replace its usage with implicit namespaces (PEP 420).
See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
for details.
!!
ep.load()(self, ep.name, value)
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'test'
E: pybuild pybuild:389: test: plugin custom failed with: exit code=1:
python3.12 setup.py test
dh_auto_test: error: pybuild --test -i python{version} -p 3.12 returned exit
code 13
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-08-28T06:15:37Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/553204/
About the archive rebuild: The build was made on debusine.debian.net,
using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/9926/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1080283: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-pyhcl Version: 0.4.4-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-pyhcl failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary make: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions dh binary --buildsystem=python_distutils --with python3 dh_testroot -O--buildsystem=python_distutils dh_prep -O--buildsystem=python_distutils debian/rules override_dh_auto_install make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions # setup.py uses this file echo "__version__ = '0.4.4'" >src/hcl/version.py pkgos-dh_auto_install --no-py2 --in-tmp + PKGOS_IN_TMP=no + echo WARNING: --no-py2 is deprecated and always on. WARNING: --no-py2 is deprecated and always on. + shift + PKGOS_IN_TMP=yes + shift + dpkg-parsechangelog -SSource + SRC_PKG_NAME=python-pyhcl + echo python-pyhcl + sed s/python-// + PY_MODULE_NAME=pyhcl + py3versions -vr + PYTHON3S=3.12 + [ yes = yes ] + TARGET_DIR=tmp + pwd + python3.12 setup.py install --install-layout=deb --root /<>/debian/tmp /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. !! self.initialize_options() warning: no files found matching 'src/hcl/parsetab.dat' + pwd + rm -rf /<>/debian/python*/usr/lib/python*/dist-packages/*.pth + pwd + rm -rf /<>/debian/tmp/usr/lib/python*/dist-packages/*.pth set -e ; for pyvers in 3.12; do \ python$pyvers setup.py test ; \ done usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:23: override_dh_auto_install] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T05:23:36Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/553056/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9862/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080286: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-xstatic-mdi Version: 1.6.50.2-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-xstatic-mdi failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions set -e ; for pyvers in 3.12; do \ python$pyvers setup.py test ; \ done /usr/lib/python3/dist-packages/setuptools/dist.py:450: SetuptoolsDeprecationWarning: Invalid dash-separated options !! Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead. By 2024-Sep-26, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. !! opt = self.warn_dash_deprecation(opt, section) /usr/lib/python3/dist-packages/setuptools/dist.py:450: SetuptoolsDeprecationWarning: Invalid dash-separated options !! Usage of dash-separated 'maintainer-email' will not be supported in future versions. Please use the underscore name 'maintainer_email' instead. By 2024-Sep-26, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. !! opt = self.warn_dash_deprecation(opt, section) /usr/lib/python3/dist-packages/setuptools/dist.py:450: SetuptoolsDeprecationWarning: Invalid dash-separated options !! Usage of dash-separated 'home-page' will not be supported in future versions. Please use the underscore name 'home_page' instead. By 2024-Sep-26, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. !! opt = self.warn_dash_deprecation(opt, section) /usr/lib/python3/dist-packages/setuptools/dist.py:653: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Build finished at 2024-08-28T05:31:42Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/553096/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9877/ If this is real
Bug#1080285: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-xstatic-magic-search Version: 0.2.5.1-4 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-xstatic-magic-search failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions set -e ; for pyvers in 3.12; do \ python$pyvers setup.py test ; \ done /usr/lib/python3/dist-packages/setuptools/dist.py:653: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:23: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Build finished at 2024-08-28T05:31:36Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/553094/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9876/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080280: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-flask-seeder
Version: 1.2.0-3
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72,
python-flask-seeder
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
byte-compiling
/<>/debian/tmp/usr/lib/python3/dist-packages/flask_seeder/generator.py
to generator.cpython-312.pyc
byte-compiling
/<>/debian/tmp/usr/lib/python3/dist-packages/flask_seeder/faker.py
to faker.cpython-312.pyc
byte-compiling
/<>/debian/tmp/usr/lib/python3/dist-packages/flask_seeder/seeder.py
to seeder.cpython-312.pyc
running install_egg_info
Copying Flask_Seeder.egg-info to
/<>/debian/tmp/usr/lib/python3/dist-packages/Flask_Seeder-1.2.0.egg-info
Skipping SOURCES.txt
running install_scripts
+ pwd
+ rm -rf /<>/debian/python*/usr/lib/python*/dist-packages/*.pth
+ pwd
+ rm -rf /<>/debian/tmp/usr/lib/python*/dist-packages/*.pth
set -e ; set -x ; for pyvers in 3.12; do \
PYTHONPATH=/<>/debian/tmp/usr/lib/python3/dist-packages
python$pyvers -m coverage run setup.py test ; \
done
+ PYTHONPATH=/<>/debian/tmp/usr/lib/python3/dist-packages
python3.12 -m coverage run setup.py test
/usr/lib/python3/dist-packages/coverage/control.py:888: CoverageWarning: No
data was collected. (no-data-collected)
self._warn("No data was collected.", slug="no-data-collected")
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'test'
make[1]: *** [debian/rules:18: override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-08-28T05:14:52Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/553006/
About the archive rebuild: The build was made on debusine.debian.net,
using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/9837/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1080284: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-xstatic Version: 1.0.3-2 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-xstatic failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions set -e && for pyvers in 3.12; do \ python$pyvers setup.py test ; \ done /<>/setup.py:11: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources /usr/lib/python3/dist-packages/setuptools/dist.py:653: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Build finished at 2024-08-28T05:30:50Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/553090/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9875/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080282: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-potr
Version: 1.0.2-5
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72, python-potr
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12/build/potr
copying src/potr/__init__.py ->
/<>/.pybuild/cpython3_3.12/build/potr
copying src/potr/utils.py -> /<>/.pybuild/cpython3_3.12/build/potr
copying src/potr/context.py ->
/<>/.pybuild/cpython3_3.12/build/potr
copying src/potr/crypt.py -> /<>/.pybuild/cpython3_3.12/build/potr
copying src/potr/proto.py -> /<>/.pybuild/cpython3_3.12/build/potr
creating /<>/.pybuild/cpython3_3.12/build/potr/compatcrypto
copying src/potr/compatcrypto/__init__.py ->
/<>/.pybuild/cpython3_3.12/build/potr/compatcrypto
copying src/potr/compatcrypto/common.py ->
/<>/.pybuild/cpython3_3.12/build/potr/compatcrypto
copying src/potr/compatcrypto/pycrypto.py ->
/<>/.pybuild/cpython3_3.12/build/potr/compatcrypto
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS='{interpreter} setup.py test -vv'
dh_auto_test
I: pybuild base:311: python3.12 setup.py test -vv
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'test'
E: pybuild pybuild:389: test: plugin custom failed with: exit code=1:
python3.12 setup.py test -vv
dh_auto_test: error: pybuild --test -i python{version} -p 3.12 returned exit
code 13
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Build finished at 2024-08-28T05:22:50Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/553054/
About the archive rebuild: The build was made on debusine.debian.net,
using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/9859/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1080281: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-mujson Version: 1.4-2 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-mujson failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary make: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions dh binary --buildsystem=python_distutils --with python3 dh_testroot -O--buildsystem=python_distutils dh_prep -O--buildsystem=python_distutils debian/rules override_dh_auto_install make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions pkgos-dh_auto_install --no-py2 --in-tmp + PKGOS_IN_TMP=no + echo WARNING: --no-py2 is deprecated and always on. WARNING: --no-py2 is deprecated and always on. + shift + PKGOS_IN_TMP=yes + shift + dpkg-parsechangelog -SSource + SRC_PKG_NAME=python-mujson + echo python-mujson + sed s/python-// + PY_MODULE_NAME=mujson + py3versions -vr + PYTHON3S=3.12 + [ yes = yes ] + TARGET_DIR=tmp + pwd + python3.12 setup.py install --install-layout=deb --root /<>/debian/tmp running install /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. !! self.initialize_options() running build running build_py creating build creating build/lib creating build/lib/mujson copying mujson/__init__.py -> build/lib/mujson running install_lib creating /<>/debian/tmp creating /<>/debian/tmp/usr creating /<>/debian/tmp/usr/lib creating /<>/debian/tmp/usr/lib/python3 creating /<>/debian/tmp/usr/lib/python3/dist-packages creating /<>/debian/tmp/usr/lib/python3/dist-packages/mujson copying build/lib/mujson/__init__.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/mujson byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/mujson/__init__.py to __init__.cpython-312.pyc running install_egg_info running egg_info creating mujson.egg-info writing mujson.egg-info/PKG-INFO writing dependency_links to mujson.egg-info/dependency_links.txt writing top-level names to mujson.egg-info/top_level.txt writing manifest file 'mujson.egg-info/SOURCES.txt' reading manifest file 'mujson.egg-info/SOURCES.txt' adding license file 'LICENSE' writing manifest file 'mujson.egg-info/SOURCES.txt' Copying mujson.egg-info to /<>/debian/tmp/usr/lib/python3/dist-packages/mujson-1.4.egg-info Skipping SOURCES.txt running install_scripts + pwd + rm -rf /<>/debian/python*/usr/lib/python*/dist-packages/*.pth + pwd + rm -rf /<>/debian/tmp/usr/lib/python*/dist-packages/*.pth set -e ; for pyvers in 3.12; do \ python$pyvers setup.py test ; \ done usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:19: override_dh_auto_install] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T05:20:10Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/553037/ About the archive re
Bug#1080278: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-autopage Version: 0.4.0-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-autopage failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] dh binary --buildsystem=python_distutils --with python3 dh_testroot -O--buildsystem=python_distutils dh_prep -O--buildsystem=python_distutils debian/rules override_dh_auto_install make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions pkgos-dh_auto_install --no-py2 --in-tmp + PKGOS_IN_TMP=no + echo WARNING: --no-py2 is deprecated and always on. WARNING: --no-py2 is deprecated and always on. + shift + PKGOS_IN_TMP=yes + shift + dpkg-parsechangelog -SSource + SRC_PKG_NAME=python-autopage + echo python-autopage + sed s/python-// + PY_MODULE_NAME=autopage + py3versions -vr + PYTHON3S=3.12 + [ yes = yes ] + TARGET_DIR=tmp + pwd + python3.12 setup.py install --install-layout=deb --root /<>/debian/tmp running install /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. !! self.initialize_options() running build running build_py creating build creating build/lib creating build/lib/autopage copying autopage/argparse.py -> build/lib/autopage copying autopage/__init__.py -> build/lib/autopage creating build/lib/autopage/tests copying autopage/tests/sinks.py -> build/lib/autopage/tests copying autopage/tests/__init__.py -> build/lib/autopage/tests copying autopage/tests/test_pager_settings.py -> build/lib/autopage/tests copying autopage/tests/test_argparse.py -> build/lib/autopage/tests copying autopage/tests/test_autopage.py -> build/lib/autopage/tests copying autopage/tests/test_line_buffer_from_input.py -> build/lib/autopage/tests running install_lib creating /<>/debian/tmp creating /<>/debian/tmp/usr creating /<>/debian/tmp/usr/lib creating /<>/debian/tmp/usr/lib/python3 creating /<>/debian/tmp/usr/lib/python3/dist-packages creating /<>/debian/tmp/usr/lib/python3/dist-packages/autopage copying build/lib/autopage/argparse.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/autopage copying build/lib/autopage/__init__.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/autopage creating /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests copying build/lib/autopage/tests/sinks.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests copying build/lib/autopage/tests/__init__.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests copying build/lib/autopage/tests/test_pager_settings.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests copying build/lib/autopage/tests/test_argparse.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests copying build/lib/autopage/tests/test_autopage.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests copying build/lib/autopage/tests/test_line_buffer_from_input.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/argparse.py to argparse.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests/sinks.py to sinks.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests/test_pager_settings.py to test_pager_settings.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests/test_argparse.py to test_argparse.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests/test_autopage.py to test_autopage.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3/dist-packages/autopage/tests/test_line_buffer_from_input.py to test_line_buffer_from_input.cpython-312.pyc running install_egg_info running egg_info creating autopage.egg-
Bug#1080279: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: python-editor Version: 1.0.3-7 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-editor failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] dh_auto_configure: warning: This feature will be removed in compat 12. debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions set -e ; for pyvers in 3.12; do \ python$pyvers setup.py test ; \ done usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Build finished at 2024-08-28T05:13:57Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/553000/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9834/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080277: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: pyemd Version: 0.5.1.54.g802fa86-2 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, pyemd failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] x86_64-linux-gnu-g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-cpython-312/pyemd/emd.o -L/usr/lib/x86_64-linux-gnu -o /<>/.pybuild/cpython3_3.12_pyemd/build/pyemd/emd.cpython-312-x86_64-linux-gnu.so debian/rules execute_before_dh_auto_test make[1]: Entering directory '/<>' for python in $(py3versions --supported) ; do \ "$python" setup.py test ; \ done /usr/lib/python3/dist-packages/setuptools/__init__.py:88: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. !! dist.fetch_build_eggs(dist.setup_requires) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:11: execute_before_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T03:51:26Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/552881/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9788/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080276: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: morfessor Version: 2.0.6-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, morfessor failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] changing mode of build/scripts-3.12/morfessor-segment from 644 to 755 changing mode of build/scripts-3.12/morfessor-evaluate from 644 to 755 debian/rules execute_before_dh_auto_test make[1]: Entering directory '/<>' python3 setup.py test usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:10: execute_before_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T02:48:35Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/552766/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9743/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080275: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: hovercraft Version: 2.7-6 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, hovercraft failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] I: pybuild base:311: python3.12 setup.py config running config debian/rules override_dh_auto_test make[1]: Entering directory '/<>' py3versions: no X-Python3-Version in control file, using supported versions set -e; for PY in python3.12; do \ http_proxy='127.0.0.1:9' https_proxy='127.0.0.1:9' python3 setup.py test; \ done usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T01:08:40Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/552643/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9699/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080274: FTBFS with setuptools >= 72: error: invalid command 'test'
Source: flent Version: 2.1.1-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, flent failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] dh_auto_configure debian/rules override_dh_auto_test make[1]: Entering directory '/<>' /usr/bin/make test PYTHON=python3 make[2]: Entering directory '/<>' python3 setup.py test -r unittests:TestRunner usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[2]: *** [Makefile:11: test] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:27: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Build finished at 2024-08-28T00:28:29Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/552584/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9674/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080272: FTBFS with setuptools 72: error: invalid command 'test'
Source: apscheduler
Version: 3.10.4-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72, apscheduler
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dh_auto_test -- --system=custom --test-args="{interpreter} setup.py test"
I: pybuild base:311: python3.12 setup.py test
/usr/lib/python3/dist-packages/setuptools/dist.py:450:
SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
Usage of dash-separated 'upload-dir' will not be supported in future
versions. Please use the underscore name 'upload_dir' instead.
By 2024-Sep-26, you need to update your project and remove deprecated
calls
or your builds will no longer be supported.
See
https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
details.
!!
opt = self.warn_dash_deprecation(opt, section)
/usr/lib/python3/dist-packages/setuptools/__init__.py:88: _DeprecatedInstaller:
setuptools.installer and fetch_build_eggs are deprecated.
!!
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
!!
dist.fetch_build_eggs(dist.setup_requires)
WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml
does not contain a tool.setuptools_scm section'
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py",
line 36, in read_pyproject
section = defn.get("tool", {})[tool_name]
^^^
KeyError: 'setuptools_scm'
/usr/lib/python3/dist-packages/setuptools/dist.py:450:
SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
Usage of dash-separated 'upload-dir' will not be supported in future
versions. Please use the underscore name 'upload_dir' instead.
By 2024-Sep-26, you need to update your project and remove deprecated
calls
or your builds will no longer be supported.
See
https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
details.
!!
opt = self.warn_dash_deprecation(opt, section)
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'test'
E: pybuild pybuild:389: test: plugin custom failed with: exit code=1:
python3.12 setup.py test
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12
--system=custom "--test-args={interpreter} setup.py test" returned exit code 13
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-08-27T23:39:54Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/552416/
About the archive rebuild: The build was made on debusine.debian.net,
using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/9607/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1080237: FTBFS with setuptools 72: error: invalid command 'test'
Source: sphinxcontrib-programoutput Version: 0.17-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, sphinxcontrib-programoutput failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] Do nothing... make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions set -e ; for i in 3.12 ; do \ PYTHONPATH=. PYTHON=python$i python$i setup.py test ; \ done /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'tests_require' warnings.warn(msg) /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3/dist-packages/setuptools/dist.py:653: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:11: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Build finished at 2024-08-28T06:11:24Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/553190/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9919/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080232: FTBFS with setuptools 72: error: invalid command 'test'
Source: python-pgpdump Version: 1.5-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-pgpdump failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] creating /<>/.pybuild/cpython3_3.12/build/pgpdump copying pgpdump/__init__.py -> /<>/.pybuild/cpython3_3.12/build/pgpdump copying pgpdump/packet.py -> /<>/.pybuild/cpython3_3.12/build/pgpdump copying pgpdump/test.py -> /<>/.pybuild/cpython3_3.12/build/pgpdump copying pgpdump/data.py -> /<>/.pybuild/cpython3_3.12/build/pgpdump copying pgpdump/utils.py -> /<>/.pybuild/cpython3_3.12/build/pgpdump copying pgpdump/__main__.py -> /<>/.pybuild/cpython3_3.12/build/pgpdump make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' py3versions: no X-Python3-Version in control file, using supported versions py3versions: no X-Python3-Version in control file, using supported versions py3versions: no X-Python3-Version in control file, using supported versions python3.12 setup.py test -vv /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:10: test-python3.12] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Build finished at 2024-08-28T05:22:04Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/553049/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9857/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080235: FTBFS with setuptools 72: E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1
Source: python-pulp
Version: 2.7.0+dfsg-3
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72, python-pulp
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
test_pulp_060 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_060) ... skipped
"solver not available"
test_pulp_061 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_061) ... skipped
"solver not available"
test_pulp_070 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_070) ... skipped
"solver not available"
test_pulp_075 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_075) ... skipped
"solver not available"
test_pulp_080 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_080)
Test the reporting of dual variables slacks and reduced costs ... skipped
"solver not available"
test_pulp_090 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_090) ... skipped
"solver not available"
test_pulp_100 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_100)
Test the ability to sequentially solve a problem ... skipped "solver not available"
test_pulp_110 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_110)
Test the ability to use fractional constraints ... skipped "solver not available"
test_pulp_120 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_120)
Test the ability to use Elastic constraints ... skipped "solver not available"
test_pulp_121 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_121)
Test the ability to use Elastic constraints ... skipped "solver not available"
test_pulp_122 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_122)
Test the ability to use Elastic constraints (penalty unchanged) ... skipped
"solver not available"
test_pulp_123 (pulp.tests.test_pulp.YAPOSIBTest.test_pulp_123)
Test the ability to use Elastic constraints (penalty unbounded) ... skipped
"solver not available"
test_timeLimit (pulp.tests.test_pulp.YAPOSIBTest.test_timeLimit) ... skipped
"solver not available"
test_unbounded_problem__is_not_valid
(pulp.tests.test_pulp.YAPOSIBTest.test_unbounded_problem__is_not_valid)
Given an unbounded problem, where x will tend to infinity ... skipped "solver
not available"
test_unset_objective_value__is_valid
(pulp.tests.test_pulp.YAPOSIBTest.test_unset_objective_value__is_valid)
Given a valid problem that does not converge, ... skipped "solver not available"
==
ERROR: test_examples (pulp.tests.test_examples.Examples_DocsTests.test_examples)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.12_pulp/build/pulp/tests/test_examples.py",
line 13, in test_examples
files = os.listdir(os.path.join(parent_dir, examples_dir))
^^
FileNotFoundError: [Errno 2] No such file or directory:
'/<>/.pybuild/cpython3_3.12_pulp/build/pulp/tests/../../examples'
--
Ran 1005 tests in 21.850s
FAILED (errors=1, skipped=885)
Trying:
x = LpVariable("x", 0, 3)
Expecting nothing
ok
Trying:
y = LpVariable("y", 0, 1)
Expecting nothing
ok
Trying:
prob = LpProblem("myProblem", const.LpMinimize)
Expecting nothing
ok
Trying:
prob += x + y <= 2
Expecting nothing
ok
Trying:
prob += -4 * x + y
Expecting nothing
ok
Trying:
status = prob.solve(PULP_CBC_CMD(msg=0))
Expecting nothing
ok
Trying:
const.LpStatus[status]
Expecting:
'Optimal'
ok
Trying:
value(x)
Expecting:
2.0
ok
1 items passed all tests:
8 tests in pulp
8 tests in 1 items.
8 passed and 0 failed.
Test passed.
Test that logic put in place for deprecation handling of indexs works
Testing 'indexs' param continues to work for LpVariable.dicts
Testing 'indexs' param continues to work for LpVariable.matrix
Testing 'indices' argument works in LpVariable.dicts
Testing 'indices' param continues to work for LpVariable.matrix
Testing invalid status
Testing continuous LP solution - export dict
Testing export dict for LP
Testing export dict MIP
Testing maximize continuous LP solution
Testing continuous LP solution - export JSON
Testing continuous LP solution - export solver dict
Testing continuous LP solution - export solver JSON
Testing reading MPS files - binary variable, no constraint names
Testing reading MPS files - integer variable
Testing reading MPS files - maximize
Testing reading MPS
Bug#1080234: FTBFS with setuptools 72: error: invalid command 'test'
Source: serpent
Version: 1.41-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72, serpent
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
dh_auto_build -O--buildsystem=pybuild
pybuild --build -i python{version} -p 3.12
I: pybuild base:311: /usr/bin/python3 setup.py build
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning:
Unknown distribution option: 'test_suite'
warnings.warn(msg)
running build
running build_py
copying serpent.py -> /<>/.pybuild/cpython3_3.12_serpent/build
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
/usr/bin/make test
make[2]: Entering directory '/<>'
python3 setup.py test
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning:
Unknown distribution option: 'test_suite'
warnings.warn(msg)
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'test'
make[2]: *** [Makefile:18: test] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Build finished at 2024-08-28T06:06:57Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/553173/
About the archive rebuild: The build was made on debusine.debian.net,
using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/9912/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1080230: FTBFS with setuptools 72: django.core.exceptions.ImproperlyConfigured
Source: python-django-swapper
Version: 1.3.0-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72,
python-django-swapper
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3 setup.py build
/usr/lib/python3/dist-packages/setuptools/__init__.py:88: _DeprecatedInstaller:
setuptools.installer and fetch_build_eggs are deprecated.
!!
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
!!
dist.fetch_build_eggs(dist.setup_requires)
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning:
Unknown distribution option: 'tests_require'
warnings.warn(msg)
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning:
Unknown distribution option: 'test_suite'
warnings.warn(msg)
WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml
does not contain a tool.setuptools_scm section'
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py",
line 36, in read_pyproject
section = defn.get("tool", {})[tool_name]
^^^
KeyError: 'setuptools_scm'
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_django-swapper/build/swapper
copying swapper/__init__.py ->
/<>/.pybuild/cpython3_3.12_django-swapper/build/swapper
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd
/<>/.pybuild/cpython3_3.12_django-swapper/build; python3.12 -m
unittest discover -v
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/lib/python3.12/unittest/__main__.py", line 18, in
main(module=None)
File "/usr/lib/python3.12/unittest/main.py", line 104, in __init__
self.parseArgs(argv)
File "/usr/lib/python3.12/unittest/main.py", line 130, in parseArgs
self._do_discovery(argv[2:])
File "/usr/lib/python3.12/unittest/main.py", line 253, in _do_discovery
self.createTests(from_discovery=True, Loader=Loader)
File "/usr/lib/python3.12/unittest/main.py", line 160, in createTests
self.test = loader.discover(self.start, self.pattern, self.top)
^^^
File "/usr/lib/python3.12/unittest/loader.py", line 310, in discover
tests = list(self._find_tests(start_dir, pattern))
^^
File "/usr/lib/python3.12/unittest/loader.py", line 366, in _find_tests
tests, should_recurse = self._find_test_path(full_path, pattern)
File "/usr/lib/python3.12/unittest/loader.py", line 442, in _find_test_path
tests = self.loadTestsFromModule(package, pattern=pattern)
^^
File "/usr/lib/python3.12/unittest/loader.py", line 103, in
loadTestsFromModule
isinstance(obj, type)
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 295,
in __getattribute__
value = super().__getattribute__(name)
^^
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 266,
in inner
self._setup()
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 82, in
_setup
raise ImproperlyConfigured(
django.core.exceptions.ImproperlyConfigured: Requested settings, but settings
are not configured. You must either define the environment variable
DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.12_django-swapper/build; python3.12 -m
unittest discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.12 returned exit
code 13
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-08-28T05:12:28Z
---
The above is just how the build ends and n
Bug#1080227: FTBFS with setuptools 72: error: invalid command 'test'
Source: python-calmjs.types Version: 1.0.1-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-calmjs.types failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions echo "Do nothing..." Do nothing... make[1]: Leaving directory '/<>' create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary make: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions dh binary --buildsystem=python_distutils --with python3 dh_testroot -O--buildsystem=python_distutils dh_prep -O--buildsystem=python_distutils debian/rules override_dh_auto_install make[1]: Entering directory '/<>' make[1]: pyversions: No such file or directory py3versions: no X-Python3-Version in control file, using supported versions pkgos-dh_auto_install --no-py2 --in-tmp + PKGOS_IN_TMP=no + echo WARNING: --no-py2 is deprecated and always on. WARNING: --no-py2 is deprecated and always on. + shift + PKGOS_IN_TMP=yes + shift + dpkg-parsechangelog -SSource + SRC_PKG_NAME=python-calmjs.types + echo python-calmjs.types + sed s/python-// + PY_MODULE_NAME=calmjs.types + py3versions -vr + PYTHON3S=3.12 + [ yes = yes ] + TARGET_DIR=tmp + pwd + python3.12 setup.py install --install-layout=deb --root /<>/debian/tmp /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3/dist-packages/setuptools/dist.py:653: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) running install /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. !! self.initialize_options() running build running build_py creating build creating build/lib creating build/lib/calmjs copying src/calmjs/__init__.py -> build/lib/calmjs creating build/lib/calmjs/types copying src/calmjs/types/__init__.py -> build/lib/calmjs/types copying src/calmjs/types/exceptions.py -> build/lib/calmjs/types creating build/lib/calmjs/types/tests copying src/calmjs/types/tests/__init__.py -> build/lib/calmjs/types/tests copying src/calmjs/types/tests/test_exceptions.py -> build/lib/calmjs/types/tests running egg_info creating src/calmjs.types.egg-info writing src/calmjs.types.egg-info/PKG-INFO writing dependency_links to src/calmjs.types.egg-info/dependency_links.txt writing namespace_packages to src/calmjs.types.egg-info/namespace_packages.txt writing requirements to src/calmjs.types.egg-info/requires.txt writing top-level names to src/calmjs.types.egg-info/top_level.txt writing manifest file 'src/calmjs.types.egg-info/SOURCES.txt' reading manifest file 'src/calmjs.types.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txt' under directory 'docs' warning: no files found matching '*.rst' under directory 'docs' warning: no files found matching '*.txt' warning: no previously-included files matching '*.pyc' found under directory 'src' warning: no previously-included files matching '*.pyo' found under directory 'src' adding license file 'LICENSE' writing manifest file 'src/calmjs.types.egg-info/SOURCES.txt' running install_lib Skipping installation of /<>/debian/tmp/usr/lib/python3/dist-packages/calmjs/__init__.py (namespace package) copying calmjs/types/__init__.py -> /<>/debian/tmp/usr/lib/python3/dist-packages/calmjs/types copying calmjs/types/exceptions.py -> /<>/debian/tmp/usr/lib/p
Bug#1080226: FTBFS with setuptools 72: error: invalid command 'test'
Source: python-calmjs.parse Version: 1.2.5-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, python-calmjs.parse failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] Installing /<>/debian/tmp/usr/lib/python3/dist-packages/calmjs.parse-1.2.5-nspkg.pth running install_scripts /usr/bin/python3.12: Error while finding module specification for 'calmjs.parse.parsers.optimize' (ModuleNotFoundError: No module named 'calmjs') + pwd + rm -rf /<>/debian/python*/usr/lib/python*/dist-packages/*.pth + pwd + rm -rf /<>/debian/tmp/usr/lib/python3/dist-packages/calmjs.parse-1.2.5-nspkg.pth set -e ; for pyvers in 3.12; do \ python$pyvers setup.py test ; \ done /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3/dist-packages/setuptools/dist.py:653: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:20: override_dh_auto_install] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T05:07:40Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/552962/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9817/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080225: FTBFS with setuptools 72: error: invalid command 'test'
Source: protobuf Version: 3.21.12-9 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, protobuf failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] PASS: google/protobuf/io/gzip_stream_unittest.sh PASS: google/protobuf/compiler/zip_output_unittest.sh PASS: protobuf-test Testsuite summary for Protocol Buffers 3.21.12 # TOTAL: 7 # PASS: 7 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 make[5]: Leaving directory '/<>/src' make[4]: Leaving directory '/<>/src' make[3]: Leaving directory '/<>/src' make[2]: Leaving directory '/<>' set -e; \ export LD_LIBRARY_PATH=/<>/src/.libs; \ cd python3 && for PYTHON in python3.12; do \ $PYTHON setup.py test --cpp_implementation; \ done /<>/python3/setup.py:11: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3/dist-packages/setuptools/dist.py:653: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:101: override_dh_auto_test-arch] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:22: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T03:46:52Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/552871/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9784/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080224: FTBFS with setuptools 72: AttributeError: 'Distribution' object has no attribute 'tests_require'
Source: nose
Version: 1.3.7-13
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72, nose
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
==
ERROR: test_setup_nosetests_command_works
(test_commands.TestCommands.test_setup_nosetests_command_works)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.12_nose/build.tests/functional_tests/test_commands.py",
line 39, in test_setup_nosetests_command_works
cmd.run()
File
"/<>/.pybuild/cpython3_3.12_nose/build.tests/nose/commands.py",
line 145, in run
if self.distribution.tests_require:
^^^
AttributeError: 'Distribution' object has no attribute 'tests_require'
>> begin captured stdout << -
/<>/.pybuild/cpython3_3.12_nose/build.tests
- >> end captured stdout << --
>> begin captured logging <<
root: DEBUG: No `packages` or `py_modules` configuration, performing automatic
discovery.
root: DEBUG: `explicit-layout` detected -- analysing {'issue191':
'/<>/.pybuild/cpython3_3.12_nose/build.tests/functional_tests/support/issue191'}
root: DEBUG: discovered packages -- ['issue191']
root: DEBUG: No `name` configuration, performing automatic discovery
root: DEBUG: Single module/package detected, name: issue191
root: INFO: running egg_info
root: INFO: creating issue191.egg-info
root: INFO: writing issue191.egg-info/PKG-INFO
root: INFO: writing dependency_links to issue191.egg-info/dependency_links.txt
root: INFO: writing top-level names to issue191.egg-info/top_level.txt
root: INFO: writing manifest file 'issue191.egg-info/SOURCES.txt'
root: INFO: reading manifest file 'issue191.egg-info/SOURCES.txt'
root: INFO: writing manifest file 'issue191.egg-info/SOURCES.txt'
- >> end captured logging << -
--
Ran 381 tests in 11.359s
FAILED (SKIP=10, errors=1)
E: pybuild pybuild:389: test: plugin custom failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.12_nose/build.tests && python3.12 -m nose
-v --with-doctest
dh_auto_test: error: pybuild --test -i python{version} -p 3.12 --system=custom
returned exit code 13
make[1]: *** [debian/rules:26: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:19: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-08-28T03:06:04Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/552799/
About the archive rebuild: The build was made on debusine.debian.net,
using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/9754/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1080223: FTBFS with setuptools 72: error: invalid command 'test'
Source: mando Version: 0.7.1-3 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, mando failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] debian/rules override_dh_auto_test make[1]: Entering directory '/<>' rm -f -r .pybuild/ python3 setup.py test /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:16: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T02:34:12Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/552746/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9736/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080222: FTBFS: /usr/include/boost/mpi/config.hpp:22:10: fatal error: mpi.h: No such file or directory
Source: gyoto Version: 2.0.2-3 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, During a test rebuild for packages affected by setuptools 72, gyoto failed to rebuild. --- [...] /usr/bin/mkdir -p swig_output /usr/bin/swig -I../include -I./../include -c++ -python -outdir swig_output -o std_wrap.cxx ./gyoto_std.i ../include/GyotoWorldline.h:856: Warning 325: Nested class not currently supported (IntegState ignored) ../include/GyotoScreen.h:0: Warning 314: 'print' is a python keyword, renaming to '_print' ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Coord1dSet ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Coord2dSet ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Grid ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Bucket ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Empty ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Range ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Indices ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Angles ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (RepeatAngle ignored) ../include/GyotoAstrobj.h:0: Warning 302: Redefinition of identifier 'Generic' by %extend ignored, gyoto.i:727: Warning 302: %extend definition of 'Generic'. ../include/GyotoComplexSpectrometer.h:0: Warning 389: operator[] ignored (consider using %extend) ../include/GyotoComplexSpectrometer.h:0: Warning 389: operator[] ignored (consider using %extend) gyoto.i:843: Warning 389: operator[] ignored (consider using %extend) ../include/GyotoProperty.h:770: Warning 325: Nested union not currently supported (setter_t ignored) ../include/GyotoProperty.h:789: Warning 325: Nested union not currently supported (getter_t ignored) ../include/GyotoProperty.h:797: Warning 325: Nested union not currently supported (setter_unit_t ignored) ../include/GyotoProperty.h:802: Warning 325: Nested union not currently supported (getter_unit_t ignored) ./gyoto_std.i:32: Warning 302: Redefinition of identifier 'array_double' ignored, gyoto.i:541: Warning 302: previous definition of 'array_double'. ./gyoto_std.i:33: Warning 302: Redefinition of identifier 'array_unsigned_long' ignored, gyoto.i:543: Warning 302: previous definition of 'array_unsigned_long'. ./gyoto_std.i:34: Warning 302: Redefinition of identifier 'array_size_t' ignored, gyoto.i:542: Warning 302: previous definition of 'array_size_t'. ../include/GyotoComplexAstrobj.h:0: Warning 389: operator[] ignored (consider using %extend) ../include/GyotoComplexAstrobj.h:0: Warning 389: operator[] ignored (consider using %extend) ../include/GyotoPolishDoughnut.h:0: Warning 314: 'lambda' is a python keyword, renaming to '_lambda' ../include/GyotoPolishDoughnut.h:0: Warning 314: 'lambda' is a python keyword, renaming to '_lambda' ../include/GyotoComplexMetric.h:0: Warning 319: No access specifier given for base class 'Gyoto::WIP' (ignored). ../include/GyotoComplexMetric.h:0: Warning 389: operator[] ignored (consider using %extend) ../include/GyotoComplexMetric.h:0: Warning 389: operator[] ignored (consider using %extend) /usr/bin/mkdir -p `dirname gyoto/std.py` cat headers/std swig_output/std.py > gyoto/std.py /usr/bin/mkdir -p swig_output /usr/bin/swig -I../include -I./../include -c++ -python -outdir swig_output -o lorene_wrap.cxx ./gyoto_lorene.i ../include/GyotoWorldline.h:856: Warning 325: Nested class not currently supported (IntegState ignored) ../include/GyotoScreen.h:0: Warning 314: 'print' is a python keyword, renaming to '_print' ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Coord1dSet ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Coord2dSet ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Grid ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Bucket ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Empty ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Range ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Indices ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (Angles ignored) ../include/GyotoScreen.h:0: Warning 325: Nested class not currently supported (RepeatAngle ignored) ../include/GyotoAstrobj.h:0: Warning 302: Redefinition of identifier 'Generic' by %extend ignored, gyoto.i:727: Warning 302: %extend definition of 'Generic'. ../include/GyotoComplexSpectrometer.h:0: Warning 389: opera
Bug#1080220: FTBFS: error: invalid command 'test'
Source: gdebi
Version: 0.9.5.7+nmu9
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian-pyt...@lists.debian.org
Usertags: setup.py-test
Dear maintainer,
During a test rebuild for packages affected by setuptools 72, gdebi
failed to rebuild.
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
test setup.
---
[...]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
xvfb-run -a python3.12 setup.py test
/<>/setup.py:15: SyntaxWarning: invalid escape sequence '\('
match = compile('.*\((.*)\).*').match(head)
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning:
Unknown distribution option: 'test_suite'
warnings.warn(msg)
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'test'
make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Build finished at 2024-08-28T00:36:39Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/552598/
About the archive rebuild: The build was made on debusine.debian.net,
using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/9680/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
Bug#1080213: FTBFS with setuptools 72: error: invalid command 'test'
Package: distro-info Version: 1.7 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, distro-info failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] dh_auto_test make -j8 test make[1]: Entering directory '/<>' ./test-debian-distro-info cd perl && ./test.pl testAlias 1..35 ok 1 - unique: Matching lists ok 2 - symmetric_difference: Matching lists ok 3 - unique: 1 Unique Item ok 4 - unique: 1 Unique Item in the haystack ok 5 - symmetric_difference: 1 Unique Item ok 6 - Debian all ok 7 - Debian devel ok 8 - Debian oldstable ok 9 - Debian stable ok 10 - Debian testing ok 11 - Debian valid ok 12 - Debian valid ok 13 - Debian invalid ok 14 - Debian supported ok 15 - Debian LTS ok 16 - Debian ELTS ok 17 - Debian unsupported ok 18 - Debian codename, invalid py3versions: no X-Python3-Version in control file, using supported versions ok 19 - Debian codename ok 20 - Debian version, invalid ok 21 - Debian version ok 22 - Ubuntu all ok 23 - Ubuntu version ok 24 - Ubuntu LTS version ok 25 - Ubuntu devel ok 26 - Ubuntu LTS ok 27 - Ubuntu stable ok 28 - Ubuntu valid ok 29 - Ubuntu invalid ok 30 - Ubuntu is_lts ok 31 - Ubuntu !is_lts ok 32 - Ubuntu !is_lts ok 33 - Ubuntu supported ok 34 - Ubuntu ESM ok 35 - Ubuntu unsupported cd python && python3.12 setup.py test testAll testDevel testOldstable testStable testSupported testLTS /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' testELTS make[1]: *** [Makefile:39: test-python] Error 1 make[1]: *** Waiting for unfinished jobs testUnsupported testTesting testFullname testRelease testSeries testCombinedShortform testReleaseDate testHelp testExactlyOne testUnrecognizedOption testUnrecognizedArguments testMissingArgumentAlias testMissingArgumentDate testMissingArgumentSeries testInvalidAlias testInvalidDate testInvalidSeries testMultipleAlias testMultipleDates testMultipleSeries testUnknownSeries testSourceDateEpoch testDays Ran [1;36m31[0m tests. [1;32mOK[0m ./test-ubuntu-distro-info testAll testDevel testLatest testLTS testStable testSupported testUnsupported testFullname testRelease testSeries testCombinedShortform testReleaseDate testHelp testExactlyOne testUnrecognizedOption testUnrecognizedArguments testMissingArgumentDate testMissingArgumentSeries testDistributionDataOutdated testInvalidDate testInvalidSeries testMultipleDates testMultipleSeries testUnknownSeries testSourceDateEpoch testDays Ran [1;36m26[0m tests. [1;32mOK[0m make[1]: Leaving directory '/<>' dh_auto_test: error: make -j8 test returned exit code 2 make: *** [debian/rules:6: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T00:08:37Z --- 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://debusine.debian.net/artifact/552534/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9652/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano
Bug#1080208: FTBFS: RuntimeError("Support for the test command was removed in Setuptools 72")
Package: click Version: 0.5.2-4 Severity: serious Tags: ftbfs Justification: ftbfs User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, click failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] make[1]: Leaving directory '/<>' dh_auto_test -O--buildsystem=autoconf make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 make[1]: Entering directory '/<>' Making check in lib make[2]: Entering directory '/<>/lib' Making check in click make[3]: Entering directory '/<>/lib/click' make check-am make[4]: Entering directory '/<>/lib/click' make[4]: Nothing to be done for 'check-am'. make[4]: Leaving directory '/<>/lib/click' make[3]: Leaving directory '/<>/lib/click' make[3]: Entering directory '/<>/lib' make[3]: Nothing to be done for 'check-am'. make[3]: Leaving directory '/<>/lib' make[2]: Leaving directory '/<>/lib' Making check in preload make[2]: Entering directory '/<>/preload' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/<>/preload' Making check in click_package make[2]: Entering directory '/<>/click_package' Making check in tests make[3]: Entering directory '/<>/click_package/tests' Making check in integration make[4]: Entering directory '/<>/click_package/tests/integration' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/<>/click_package/tests/integration' make[4]: Entering directory '/<>/click_package/tests' make[4]: Nothing to be done for 'check-am'. make[4]: Leaving directory '/<>/click_package/tests' make[3]: Leaving directory '/<>/click_package/tests' make[3]: Entering directory '/<>/click_package' make[3]: Nothing to be done for 'check-am'. make[3]: Leaving directory '/<>/click_package' make[2]: Leaving directory '/<>/click_package' Making check in conf make[2]: Entering directory '/<>/conf' Making check in databases make[3]: Entering directory '/<>/conf/databases' make[3]: Nothing to be done for 'check'. make[3]: Leaving directory '/<>/conf/databases' make[3]: Entering directory '/<>/conf' make[3]: Nothing to be done for 'check-am'. make[3]: Leaving directory '/<>/conf' make[2]: Leaving directory '/<>/conf' Making check in debhelper make[2]: Entering directory '/<>/debhelper' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/<>/debhelper' Making check in init make[2]: Entering directory '/<>/init' Making check in systemd make[3]: Entering directory '/<>/init/systemd' make[3]: Nothing to be done for 'check'. make[3]: Leaving directory '/<>/init/systemd' make[3]: Entering directory '/<>/init' make[3]: Nothing to be done for 'check-am'. make[3]: Leaving directory '/<>/init' make[2]: Leaving directory '/<>/init' Making check in schroot make[2]: Entering directory '/<>/schroot' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/<>/schroot' Making check in click-service make[2]: Entering directory '/<>/click-service' Making check in tests make[3]: Entering directory '/<>/click-service/tests' make test-runner.sh test-fixure-wrapper.sh install-click.sh install-click-not-exists.sh install-click-no-perms.sh remove-click.sh remove-click-preinstalled.sh remove-click-not-installed.sh make[4]: Entering directory '/<>/click-service/tests' make[4]: Nothing to be done for 'test-runner.sh'. make[4]: Nothing to be done for 'test-fixure-wrapper.sh'. make[4]: Nothing to be done for 'install-click.sh'. make[4]: Nothing to be done for 'install-click-not-exists.sh'. make[4]: Nothing to be done for 'install-click-no-perms.sh'. make[4]: Nothing to be done for 'remove-click.sh'. make[4]: Nothing to be done for 'remove-click-preinstalled.sh'. make[4]: Nothing to be done for 'remove-click-not-installed.sh'. make[4]: Leaving directory '/<>/click-service/tests' make check-TESTS make[4]: Entering directory '/<>/click-service/tests' make[5]: Entering directory '/<>/click-service/tests' PASS: install-click-not-exists.sh PASS: install-click-no-perms.sh PASS: remove-click-not-installed.sh PASS: install-click.sh PASS: remove-click.sh PASS: remove-click-preinstalled.sh Testsuite summary for click 0.5.2 # TOTAL: 6 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 make[5]: Leaving directory '/<>/click-service/tests' make[4]: Leaving directory '/<>/click-service/tests' make[3]: Leaving directory '/<>/click-service/tests' make[3]: Entering directory '
Bug#1080122: Fallout from setuptools dropping the test command
FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1026543: Fallout from setuptools dropping the test command
FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1079205: marked as pending in beautifulsoup4
Control: tag -1 pending Hello, Bug #1079205 in beautifulsoup4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/beautifulsoup4/-/commit/74bf8cdea0091ef552595eb01822d949035cdbf3 Patch: Support for lxml 5.3.0. Avoid triggering a DeprecationWarning that was failing tests. (Closes: #1079205) (this message was generated automatically) -- Greetings https://bugs.debian.org/1079205
Bug#1070658: FTBFS: error: expected ‘)’ before ‘maxLength’
Source: clickhouse Version: 18.16.1+ds-7.4 Severity: serious Tags: ftbfs Justification: ftbfs clickhouse FTBFS in unstable: [ 87%] Building CXX object dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o cd /<>/obj-x86_64-linux-gnu/dbms && /usr/bin/c++ -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_NO_LIB -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -Ddbms_EXPORTS -I/<>/contrib/cityhash102/include -I/<>/libs/libpocoext/include -I/<>/libs/libmysqlxx/include -I/<>/contrib/libbtrie/include -isystem /<>/contrib/libdivide -isystem /<>/dbms/src -isystem /<>/obj-x86_64-linux-gnu/dbms/src -isystem /<>/contrib/libpcg-random/include -isystem /<>/libs/libcommon/include -isystem /<>/obj-x86_64-linux-gnu/libs/libcommon/include -isystem /usr/include/metrohash -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fno-omit-frame-pointer -Wall -Wnon-virtual-dtor -Wextra -O2 -g -DNDEBUG -O3 -std=c++17 -flto=auto -fno-fat-lto-objects -fPIC -fno-tree-loop-distribute-patterns -MD -MT dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o -MF CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o.d -o CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o -c /<>/dbms/src/Storages/MergeTree/LevelMergeSelector.cpp In file included from /<>/dbms/src/Interpreters/InterserverIOHandler.h:8, from /<>/dbms/src/Storages/MergeTree/DataPartsExchange.h:3, from /<>/dbms/src/Storages/MergeTree/DataPartsExchange.cpp:1: /usr/include/Poco/BinaryWriter.h:137:14: error: expected ‘)’ before ‘maxLength’ 137 | void writeCString(const char* cString, std::streamsize maxLength = DEFAULT_MAX_CSTR_LENGTH); | ^~~~ /usr/include/Poco/BinaryWriter.h:137:14: note: to match this ‘(’ 137 | void writeCString(const char* cString, std::streamsize maxLength = DEFAULT_MAX_CSTR_LENGTH); | ^~~~ Full build log: https://debusine.debian.net/artifact/66597/clickhouse_18.16.1+ds-7.4_amd64-2024-05-06T16:48:46Z.build Stefano
Bug#1068255: marked as pending in dh-python
Control: tag -1 pending Hello, Bug #1068255 in dh-python reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/tools/dh-python/-/commit/5406e503c4428ae3b019f2078146a1ea2dfc2fa5 dh_python3: Don't rename _module to module. (Closes: #1068255) (this message was generated automatically) -- Greetings https://bugs.debian.org/1068255
Bug#1063989: marked as pending in xonsh
Control: tag -1 pending Hello, Bug #1063989 in xonsh reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/xonsh/-/commit/a6106cfef2c398408365d976bfde9efb1895b53f New upstream release. * New upstream release. - Supports pytest 8. (Closes: #1063989) (this message was generated automatically) -- Greetings https://bugs.debian.org/1063989
Bug#1066764: marked as pending in python-authlib
Control: tag -1 pending Hello, Bug #1066764 in python-authlib reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-authlib/-/commit/1f6db06f30d70ef0cc3df5dbb4d669da7ce7a38d Unset http_proxy and https_proxy for client test. (Closes: #1066764) (this message was generated automatically) -- Greetings https://bugs.debian.org/1066764
Bug#1058132: marked as pending in python-mitogen
Control: tag -1 pending Hello, Bug #1058132 in python-mitogen reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-mitogen/-/commit/d017ecfea882adde47ddc3a7b3a58355babb6a28 Patch: Python 3.12 support. (Closes: #1058132, 1061755) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058132
Bug#1064689: marked as pending in objgraph
Control: tag -1 pending Hello, Bug #1064689 in objgraph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/objgraph/-/commit/a229c89ca98f31735686636bb6ec40f10bf1f735 Run tests using upstream's test.py, not pytest. (Closes: #1064689) (this message was generated automatically) -- Greetings https://bugs.debian.org/1064689
Bug#1064213: incus-agent: Incus Agent never starts due to ConditionPathExists
Package: incus-agent Version: 0.5.1-3 Severity: serious ... Feb 18 14:31:55 debian systemd[1]: incus-agent.service - Incus - agent was skipped because of an unmet condition check (ConditionPathExists=/dev/virtio-ports/org.linuxcontainers.incus). ... Feb 18 14:31:55 debian systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files... Feb 18 14:31:55 debian systemd[1]: Started systemd-udevd.service - Rule-based Manager for Device Events and Files. ... Because the systemd unit declares DefaultDependencies=no, it attempts to start incus-agent before systemd-udevd has started, and so the path doesn't exist yet. I can't see any obvious way to delay the condition check, I think it's best to just remove it, and allow the unit to quietly fail. Stefano
Bug#1058198: marked as pending in autopep8
Control: tag -1 pending Hello, Bug #1058198 in autopep8 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/autopep8/-/commit/4872f13d07c9dff7ae5b3d1ab5a82c7e244a8a47 Patch: Python 3.12 support. (Closes: #1058198) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058198
Bug#1058172: unattended-upgrades: diff for NMU version 2.9.1+nmu4
Control: tags 1058172 + patch
Control: tags 1058172 + pending
Dear maintainer,
I've prepared an NMU for unattended-upgrades (versioned as 2.9.1+nmu4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
Stefano
diff -Nru unattended-upgrades-2.9.1+nmu3/debian/changelog unattended-upgrades-2.9.1+nmu4/debian/changelog
--- unattended-upgrades-2.9.1+nmu3/debian/changelog 2022-12-31 16:59:00.0 -0400
+++ unattended-upgrades-2.9.1+nmu4/debian/changelog 2024-01-22 16:11:59.0 -0400
@@ -1,3 +1,11 @@
+unattended-upgrades (2.9.1+nmu4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Don't run pyflakes, it dropped support for type comments.
+(Closes: #1058172)
+
+ -- Stefano Rivera Mon, 22 Jan 2024 16:11:59 -0400
+
unattended-upgrades (2.9.1+nmu3) unstable; urgency=medium
* test: don't confuse -dbg and -unsigned with current running kernel
diff -Nru unattended-upgrades-2.9.1+nmu3/test/test_pyflakes.py unattended-upgrades-2.9.1+nmu4/test/test_pyflakes.py
--- unattended-upgrades-2.9.1+nmu3/test/test_pyflakes.py 2022-12-31 16:59:00.0 -0400
+++ unattended-upgrades-2.9.1+nmu4/test/test_pyflakes.py 2024-01-22 16:11:59.0 -0400
@@ -7,6 +7,8 @@
""" ensure that the tree is pyflakes clean """
def test_pyflakes_clean(self):
+# https://github.com/PyCQA/pyflakes/issues/683
+self.skipTest("not clean, pyflakes no longer supports type comments")
top_src_dir = os.path.join(os.path.dirname(__file__), "..")
targets = [
top_src_dir,
Bug#1058089: multiprocess: FTBFS: KeyError: '/psm_00befb89'
Hi 1058089 (2024.01.21_17:19:38_-0400) > This package ships a separate version of the source for each python 3.X > version. So, this requires a new upstream release, git snapshot, or > a patch with the 3.12 tree. Oh, no, it does have the py3.12 dir. Never mind. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1058089: multiprocess: FTBFS: KeyError: '/psm_00befb89'
This package ships a separate version of the source for each python 3.X version. So, this requires a new upstream release, git snapshot, or a patch with the 3.12 tree. https://github.com/uqfoundation/multiprocess/commits/master/py3.12 Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1056505: marked as pending in python-stack-data
Control: tag -1 pending Hello, Bug #1056505 in python-stack-data reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-stack-data/-/commit/9666fea069e975f1df166e37b1a4146e237ab88b Write an autopkgtest that calls pybuild. We can't use autopkgtest-pkg-pybuild, as version.py isn't built yet. In combination with work in cython, this Closes: #1056505. (this message was generated automatically) -- Greetings https://bugs.debian.org/1056505
Bug#1056511: marked as pending in python-urllib3
Control: tag -1 pending Hello, Bug #1056511 in python-urllib3 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-urllib3/-/commit/5c1f30f127d360c60adfcce917f740275a51ca7b Patch: Fix tests under Python 3.12. (Closes: #1056511) (this message was generated automatically) -- Greetings https://bugs.debian.org/1056511
Bug#1056872: marked as pending in cython
Control: tag -1 pending Hello, Bug #1056872 in cython reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/cython/-/commit/a8803eb6c512dbca7eb10fc6d652c24630760145 Patch: pyximport: Avoid chdir() and relative paths. (Closes: #1056872) (this message was generated automatically) -- Greetings https://bugs.debian.org/1056872
Bug#1056483: python-memory-profiler's autopkg tests fail with Python 3.12
Note: This package is no longer maintained upstream: https://github.com/pythonprofilers/memory_profiler/issues/383 Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1056414: marked as pending in ipython4
Control: tag -1 pending Hello, Bug #1056414 in ipython4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/ipython/-/commit/461ff4ff6c2bfb35567884ea240bab29019cf25f New upstream release. * New upstream release. - Adds support for Python 3.12. (Closes: #1056414) (this message was generated automatically) -- Greetings https://bugs.debian.org/1056414
Bug#1055570: marked as pending in lazy-object-proxy
Control: tag -1 pending Hello, Bug #1055570 in lazy-object-proxy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/lazy-object-proxy/-/commit/3e78c4e1840467d470cc282a79e9262c5e11b670 New upstream release. * New upstream release. - Supports Python 3.12 (Closes: #1055570, 1058384) (this message was generated automatically) -- Greetings https://bugs.debian.org/1055570
Bug#1055568: marked as pending in m2crypto
Control: tag -1 pending Hello, Bug #1055568 in m2crypto reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/m2crypto/-/commit/f00ff93bd40edb1647441943f0223b91e2cd8900 New upstream release. * New upstream release. - Supports Python 3.12. (Closes: #1055568, 1040103) (this message was generated automatically) -- Greetings https://bugs.debian.org/1055568
Bug#1052849: marked as pending in python-pkginfo
Control: tag -1 pending Hello, Bug #1052849 in python-pkginfo reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-pkginfo/-/commit/84978dbed4417cd40d3fc3eb04ee0385bdb5fe33 Run the build-time tests with tox, so that the package is installed. Closes: #1052849 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052849
Bug#1052849: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Hi Andreas (2024.01.11_17:48:43_+) > I've fixed the two other bugs in python-pkginfo and upgraded to latest > upstream. Unfortunately I have no clue about this issue. The test is expecting the module to be installed in the test environment. Either we could try harder to emulate that, or skip the tests. I committed a patch to run the test inside tox, which will install it in a virtualenv before running the test. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1059913: marked as pending in setuptools-scm
Control: tag -1 pending Hello, Bug #1059913 in setuptools-scm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/setuptools-scm/-/commit/5dd92fba07814c9fd6c41f911e0bd1ba23828c8e Explicitly depend on python3-setuptools (Closes: #1059913) (this message was generated automatically) -- Greetings https://bugs.debian.org/1059913
Bug#1052856: marked as pending in httpbin
Control: tag -1 pending Hello, Bug #1052856 in httpbin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/httpbin/-/commit/5cb1ee47ba39aab5815289108a9b54c042dc8441 Patch: Support Flask >= 2.3.0, and avoid deprecation warnings in >= 2.2.0. (Closes: #1052856) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052856
Bug#1058096: marked as pending in xonsh
Control: tag -1 pending Hello, Bug #1058096 in xonsh reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/xonsh/-/commit/5b83ef4462292c31069c63514d4d7f86ebe85283 Patch: Support Sphinx >= 5. (Closes: #1058096) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058096
