Bug#1084042: ros-geometry2: FTBFS: FAILURE: Package [tf2_kdl] for test node [tf2_kdl/test_kdl] does not exist
Package: src:ros-geometry2 Version: 0.7.7-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: dh_auto_configure --buildsystem=cmake --builddirectory=/<>/.pybuild/cpython3_3.12/build -- -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python3.12 -DPYTHON_LIBRARY:FILEPATH=/usr/lib/python3.12/config-3.12-x86_64-linux-gnu/libpython3.12.so -DPYTHON_INCLUDE_DIR:PATH=/usr/include/python3.12 -DPython_EXECUTABLE=/usr/bin/python3.12 -DPython_LIBRARY=/usr/lib/python3.12/config-3.12-x86_64-linux-gnu/libpython3.12.so -DPython_INCLUDE_DIR=/usr/include/python3.12 -DPython3_EXECUTABLE=/usr/bin/python3.12 -DPython3_LIBRARY=/usr/lib/python3.12/config-3.12-x86_64-linux-gnu/libpython3.12.so -DPython3_INCLUDE_DIR=/usr/include/python3.12 -DPYVER=3.12 cd .pybuild/cpython3_3.12/build && 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/x86_64-linux-gnu -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python3.12 -DPYTHON_LIBRARY:FILEPATH=/usr/lib/python3.12/config-3.12-x86_64-linux-gnu/libpython3.12.so -DPYTHON_INCLUDE_DIR:PATH=/usr/include/python3.12 -DPython_EXECUTABLE=/usr/bin/python3.12 -DPython_LIBRARY=/usr/lib/python3.12/config-3.12-x86_64-linux-gnu/libpython3.12.so -DPython_INCLUDE_DIR=/usr/include/python3.12 -DPython3_EXECUTABLE=/usr/bin/python3.12 -DPython3_LIBRARY=/usr/lib/python3.12/config-3.12-x86_64-linux-gnu/libpython3.12.so -D Python3_INCLUDE_DIR=/usr/include/python3.12 -DPYVER=3.12 ../../.. CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. [... snipped ...] Error: TF_NO_CHILD_FRAME_ID: Ignoring transform from authority "authority1" because child_frame_id not set at line 227 in ./tf2/src/buffer_core.cpp Error: TF_NO_FRAME_ID: Ignoring transform with child_frame_id "" from authority "authority1" because frame_id not set at line 233 in ./tf2/src/buffer_core.cpp Error: TF_DENORMALIZED_QUATERNION: Ignoring transform for child_frame_id "" from authority "authority1" because of an invalid quaternion in the transform (0.00 0.00 0.00 0.00) at line 255 in ./tf2/src/buffer_core.cpp [ OK ] tf2.setTransformFail (0 ms) [ RUN ] tf2.setTransformValid [ OK ] tf2.setTransformValid (0 ms) [ RUN ] tf2.setTransformInvalidQuaternion Error: TF_DENORMALIZED_QUATERNION: Ignoring transform for child_frame_id "child" from authority "authority1" because of an invalid quaternion in the transform (0.00 0.00 0.00 0.00) at line 255 in ./tf2/src/buffer_core.cpp [ OK ] tf2.setTransformInvalidQuaternion (0 ms) [--] 3 tests from tf2 (0 ms total) [--] 2 tests from tf2_lookupTransform [ RUN ] tf2_lookupTransform.LookupException_Nothing_Exists [ OK ] tf2_lookupTransform.LookupException_Nothing_Exists (0 ms) [ RUN ] tf2_lookupTransform.LookupException_One_Exists [ OK ] tf2_lookupTransform.LookupException_One_Exists (0 ms) [--] 2 tests from tf2_lookupTransform (0 ms total) [--] 2 tests from tf2_canTransform [ RUN ] tf2_canTransform.Nothing_Exists [ OK ] tf2_canTransform.Nothing_Exists (0 ms) [ RUN ] tf2_canTransform.One_Exists [ OK ] tf2_canTransform.One_Exists (0 ms) [--] 2 tests from tf2_canTransform (0 ms total) [--] 1 test from tf2_chainAsVector [ RUN ] tf2_chainAsVector.chain_v_configuration [ OK ] tf2_chainAsVector.chain_v_configuration (0 ms) [--] 1 test from tf2_chainAsVector (0 ms total) [--] 2 tests from tf2_walkToTopParent [ RUN ] tf2_walkToTopParent.walk_i_configuration [ OK ] tf2_walkToTopParent.walk_i_configuration (0 ms) [ RUN ] tf2_walkToTopParent.walk_v_configuration [ OK ] tf2_walkToTopParent.walk_v_configuration (0 ms) [--] 2 tests from tf2_walkToTopParent (0 ms total) [--] Global test environment tear-down [==] 10 tests from 5 test suites ran. (0 ms total) [ PASSED ] 10 tests. -- run_tests.py: execute commands /<>/.pybuild/cpython3_3.12
Bug#1083127: opencascade FTBFS: error: invalid conversion from ‘unsigned char*’ to ‘const char*’ [-fpermissive]
El 2/10/24 a las 19:33, Tobias Frost escribió: On Wed, Oct 02, 2024 at 07:16:18PM +0200, Santiago Vila wrote: Tobias: Can you handle this as the usual uploader? Or maybe it would help if I make a "team upload"? I can handle it tomorrow, but be very welcome to do an team upload as well! Ok. I went ahead and did the upload, since it was a completely minor change. (I checked that it works by doing a test build). Thanks a lot. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083127: opencascade FTBFS: error: invalid conversion from ‘unsigned char*’ to ‘const char*’ [-fpermissive]
El 2/10/24 a las 7:44, Francesco Ballarin escribió:
FYI, I am reasonably sure that
https://github.com/Open-Cascade-SAS/OCCT/commit/7236e83dcc1e7284e66dc61e612154617ef715d6.patch
will fix the issue.
Great. I've converted the above patch to Debian form (see attach).
(but it's untested yet).
Tobias: Can you handle this as the usual uploader?
Or maybe it would help if I make a "team upload"?
Thanks.commit e16744ea146ef4a39fe2f3c0f7b4dfb3ad14be95
Author: Santiago Vila
Date: Wed Oct 2 15:05:00 2024 +0200
Use auto instead of specific type. Closes: #1083127.
diff --git a/debian/patches/0013-use-auto-instead-of-specific-type.patch
b/debian/patches/0013-use-auto-instead-of-specific-type.patch
new file mode 100644
index 0..aa18f6187
--- /dev/null
+++ b/debian/patches/0013-use-auto-instead-of-specific-type.patch
@@ -0,0 +1,20 @@
+From: dpasukhi
+Subject: [PATCH] 0033808: Coding - FreeType Use unsigned point and contour
indexing in `FT_Outline`
+Bug-Debian: https://bugs.debian.org/1083127
+
+Changes to auto instead of specific type
+---
+ src/StdPrs/StdPrs_BRepFont.cxx | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/src/StdPrs/StdPrs_BRepFont.cxx
b/src/StdPrs/StdPrs_BRepFont.cxx
+@@ -457,7 +457,7 @@
+ for (short aContour = 0, aStartIndex = 0; aContour < anOutline->n_contours;
++aContour)
+ {
+ const FT_Vector* aPntList = &anOutline->points[aStartIndex];
+-const char* aTags = &anOutline->tags[aStartIndex];
++const auto* aTags = &anOutline->tags[aStartIndex];
+ const short anEndIndex = anOutline->contours[aContour];
+ const short aPntsNb= (anEndIndex - aStartIndex) + 1;
+ aStartIndex = anEndIndex + 1;
diff --git a/debian/patches/series b/debian/patches/series
index 6e3d95104..054544d09 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -12,3 +12,4 @@ do-not-use-doxygen-searchengine.patch
0010-fix-cmake-module.patch
0011-cmake-workaround-tbbmemory.patch
0012-cmake-do-not-export-ffile-prefix.patch
+0013-use-auto-instead-of-specific-type.patch
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1082747: cod-tools: FTBFS (only) on riscv64
El 29/9/24 a las 20:21, Aurelien Jarno escribió: 1) Defining the rule with an absolute path: Great! This one looks good enough for me. I'm going to make a team upload including that fix. (I've tested and it fixes the ftbfs problem when using make --shuffle, so hopefully it will also work for riscv64). In a later release we might consider dropping --no-parallel, but that will require more testing. Thanks a lot! -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1082999: ros-bond-core: FTBFS: ERROR: The following tests failed to run: * testexercise_cpp_bond
Package: src:ros-bond-core Version: 1.8.6-10 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure cd obj-x86_64-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/x86_64-linux-gnu .. CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- 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 Deprecation Warning at bond/CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel -- Using CMAKE_PREFIX_PATH: -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.12.6", minimum required is "3") -- Using PYTHON_EXECUTABLE: /usr/bin/python3 -- Using Debian Python package layout -- Using empy: /usr/bin/empy -- Using CATKIN_ENABLE_TESTING: ON -- Call enable_testing() -- Using CATKIN_TEST_RESULTS_DIR: /<>/obj-x86_64-linux-gnu/test_results -- GTest is available -- GMock is not available. Please install libgmock-dev to enable tests involving GMock. -- nosetests not found, Python tests can not be run (try installing package 'python3-nose') -- Found Threads: TRUE -- catkin 0.8.10 -- BUILD_SHARED_LIBS is on -- Using these message generators: gencpp;genlisp;genpy -- bond: 2 messages, 0 services CMake Deprecation Warning at smclib/CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel -- Using CMAKE_PREFIX_PATH: -- Using PYTHON_EXECUTABLE: /usr/bin/python3 -- Using Debian Python package layout -- Using empy: /usr/bin/empy -- Using CATKIN_ENABLE_TESTING: ON -- Call enable_testing() -- Using CATKIN_TEST_RESULTS_DIR: /<>/obj-x86_64-linux-gnu/test_results -- GTest is available -- GMock is not available. Please install libgmock-dev to enable tests involving GMock. -- nosetests not found, Python tests can not be run (try installing package 'python3-nose') -- catkin 0.8.10 -- BUILD_SHARED_LIBS is on CMake Deprecation Warning at bondcpp/CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. CMake Warning (dev) at bondcpp/CMakeLists.txt:4 (find_package): Policy CMP0167 is not set: The FindBoost module is removed. Run "cmake --help-policy CMP0167" for policy details. Use the cmake_policy command to set the policy and suppress this warning. This warning is for project developers. Use -Wno-dev to suppress it. -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.83.0/BoostConfig.cmake (found version "1.83.0") found components: date_time thread -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel -- Using CMAKE_PREFIX_PATH: -- Using PYTHON_EXECUTABLE: /usr/bin/python3 -- Using Debian Python package layout -- Using empy: /usr/bin/empy -- Using CATKIN_ENABLE_TESTING: ON -- Call enable_testing() -- Using CATKIN_TEST_RESULTS_DIR: /<>/obj-x86_64-linux-gnu/test_results -- GTest is available -- GMock is not available. Please install libgmock-dev to enable tests involving GMock. -- nosetests not found, Python tests can not be run (try installing package 'python3-
Bug#1082978: ros-interactive-markers: FTBFS: ERROR: The following tests failed to run: * testserver_test
Package: src:ros-interactive-markers Version: 1.12.0-9 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=cmake dh_update_autotools_config -O--buildsystem=cmake dh_autoreconf -O--buildsystem=cmake dh_auto_configure -O--buildsystem=cmake cd obj-x86_64-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/x86_64-linux-gnu .. CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- 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 -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel -- Using CMAKE_PREFIX_PATH: -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.12.6", minimum required is "3") -- Using PYTHON_EXECUTABLE: /usr/bin/python3 -- Using Debian Python package layout -- Using empy: /usr/bin/empy -- Using CATKIN_ENABLE_TESTING: ON -- Call enable_testing() -- Using CATKIN_TEST_RESULTS_DIR: /<>/obj-x86_64-linux-gnu/test_results -- GTest is available -- GMock is not available. Please install libgmock-dev to enable tests involving GMock. -- nosetests not found, Python tests can not be run (try installing package 'python3-nose') -- Found Threads: TRUE -- catkin 0.8.10 -- BUILD_SHARED_LIBS is on -- Using these message generators: gencpp;genlisp;genpy -- Configuring done (1.0s) -- Generating done (0.0s) 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 -- Build files have been written to: /<>/obj-x86_64-linux-gnu dh_auto_build -O--buildsystem=cmake cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install --strip-program=true" VERBOSE=1 make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/interactive_markers.dir/build.make CMakeFiles/interactive_markers.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/interactive_markers.dir/DependInfo.cmake "--color=" make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/interactive_markers.dir/build.make CMakeFiles/interactive_markers.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 28%] Building CXX object CMakeFiles/interactive_markers.dir/src/tools.cpp.o [ 28%] Building CXX object CMakeFiles/interactive_markers.dir/src/interactive_marker_server.cpp.o /usr/bin/c++ -DINTERACTIVE_MARKERS_BUILDING_LIBRARY -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 -DROS_PACKAGE_NAME=\"interactive_markers\" -Dinteractive_markers_EXPORTS -I/<>/include -I/usr/include/xmlrpcpp -I/usr/include/eigen3 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MT CMakeFiles/interactive_markers.dir/src/interactive_marker_server.cpp.o -MF CMakeFiles/interactive_markers.dir/src/interactive_marker_server.cpp.o.d -o CMakeFiles/interactive_markers.dir/src/interactive_marker_server.cpp.o -c /<>/src/interactive_marker_server.cpp /usr/bin/c++ -DINTERACTIVE_MARKERS_BUILDING_LIBRARY -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 -DROS_PACKAGE_NAME=\"interactive_markers\" -Dinteractive_mark
Bug#1082977: ros-dynamic-reconfigure: FTBFS: ERROR: The following tests failed to run: * testsimple_cpp_client_test
Package: src:ros-dynamic-reconfigure Version: 1.7.3-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=cmake dh_update_autotools_config -O--buildsystem=cmake dh_autoreconf -O--buildsystem=cmake dh_auto_configure -O--buildsystem=cmake cd obj-x86_64-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/x86_64-linux-gnu .. CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- 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 -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel -- Using CMAKE_PREFIX_PATH: -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.12.6", minimum required is "3") -- Using PYTHON_EXECUTABLE: /usr/bin/python3 -- Using Debian Python package layout -- Using empy: /usr/bin/empy -- Using CATKIN_ENABLE_TESTING: ON -- Call enable_testing() -- Using CATKIN_TEST_RESULTS_DIR: /<>/obj-x86_64-linux-gnu/test_results -- GTest is available -- GMock is not available. Please install libgmock-dev to enable tests involving GMock. -- nosetests not found, Python tests can not be run (try installing package 'python3-nose') -- Found Threads: TRUE -- catkin 0.8.10 -- BUILD_SHARED_LIBS is on -- Using these message generators: gencpp;genlisp;genpy CMake Warning (dev) at CMakeLists.txt:5 (find_package): Policy CMP0167 is not set: The FindBoost module is removed. Run "cmake --help-policy CMP0167" for policy details. Use the cmake_policy command to set the policy and suppress this warning. This warning is for project developers. Use -Wno-dev to suppress it. -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.83.0/BoostConfig.cmake (found version "1.83.0") -- dynamic_reconfigure: 10 messages, 1 services CMake Warning (dev) at cmake/dynamic_reconfigure-macros.cmake:128 (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): cmake/dynamic_reconfigure-macros.cmake:89 (dynreconf_called) CMakeLists.txt:28 (generate_dynamic_reconfigure_options) This warning is for project developers. Use -Wno-dev to suppress it. -- Found PythonInterp: /usr/bin/python3 (found version "3.12.6") -- Installing devel-space wrapper /<>/scripts/dynparam to /<>/obj-x86_64-linux-gnu/devel/lib/dynamic_reconfigure -- Configuring done (1.3s) -- Generating done (0.0s) 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 -- Build files have been written to: /<>/obj-x86_64-linux-gnu dh_auto_build -O--buildsystem=cmake cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install --strip-program=true" VERBOSE=1 make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/_dynamic_reconfigure_generate_messages_check_deps_Reconfigure.dir/build.make CMakeFiles/_dynamic_reconfigure_generate_messages_check_deps_Reconfigure.dir/depend make -f CMakeFiles/std_msgs_generate_messages_py.dir/build.make CMakeFiles/std_msgs_generate_messages_py.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix
Bug#1082747: cod-tools: FTBFS (only) on riscv64
tools/help2man scripts/utf8-to-cif --bugs-email cod-b...@ibt.lt > doc/man/utf8-to-cif.1 make[1]: *** No rule to make target 'doc/man/cif_list_tags.1', needed by 'man'. Stop. make[1]: Leaving directory '/<>' Hi. For the record: I get a similar failure on amd64 when using "make --shuffle". I have not announced this anywhere yet, but you can find a build log for cod-tools here in the build-logs directory: https://people.debian.org/~sanvila/make-shuffle/ So, because it happens easily when using make --shuffle, I believe it's a Makefile bug. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1082688: node-shiny-server: FTBFS: TypeError: Cannot read properties of undefined (reading 'define')
Package: src:node-shiny-server Version: 1.5.20.1002-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' # provide a fake shiny-server executable pointing to debian packaged nodejs # See external/node/CMakeLists.txt for details mkdir -p ext/node/bin ln -s /usr/bin/nodejs ext/node/bin/shiny-server dh_auto_configure -- -DCMAKE_INSTALL_PREFIX=/usr/lib cd obj-x86_64-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/x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX=/usr/lib .. CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- 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 CMakeLists.txt:94 (exec_program): Policy CMP0153 is not set: The exec_program command should not be called. Run "cmake --help-policy CMP0153" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Use execute_process() instead. This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring done (0.4s) -- Generating done (0.0s) CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY CMAKE_FIND_USE_PACKAGE_REGISTRY CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_RUNSTATEDIR CMAKE_INSTALL_SYSCONFDIR FETCHCONTENT_FULLY_DISCONNECTED -- Build files have been written to: /<>/obj-x86_64-linux-gnu ln -s obj-x86_64-linux-gnu build make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install --strip-program=true" VERBOSE=1 make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f src/CMakeFiles/shiny-server.dir/build.make src/CMakeFiles/shiny-server.dir/depend make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src /<>/obj-x86_64-linux-gnu/src/CMakeFiles/shiny-server.dir/DependInfo.cmake "--color=" make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f src/CMakeFiles/shiny-server.dir/build.make src/CMakeFiles/shiny-server.dir/build make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 50%] Building CXX object src/CMakeFiles/shiny-server.dir/launcher.cc.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT src/CMakeFiles/shiny-server.dir/launcher.cc.o -MF CMakeFiles/shiny-server.dir/launcher.cc.o.d -o CMakeFiles/shiny-server.dir/launcher.cc.o -c /<>/src/launcher.cc /<>/src/launcher.cc: In function ‘int main(int, char**)’: /<>/src/launcher.cc:38:13: warning: ignoring return value of ‘int daemon(int, int)’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 38 | daemon(1, 0); | ~~^~ [100%] Linking CXX executable /<>/bin/shiny-server cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/shiny-server.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ff
Bug#1082135: sumo: FTBFS randomly due to dh_installdocs misbehavior (?)
Package: src:sumo,debhelper,doxygen
Severity: important
Dear maintainer:
During a rebuild of all packages in unstable, the package "sumo" failed to
build:
[...]
debian/rules binary
dh binary --builddirectory=/<>/debian/build --with python3
dh_update_autotools_config
-O--builddirectory=/<>/sumo-1.18.0\+dfsg/debian/build
dh_autoreconf -O--builddirectory=/<>/sumo-1.18.0\+dfsg/debian/build
dh_auto_configure
-O--builddirectory=/<>/sumo-1.18.0\+dfsg/debian/build
cd debian/build && 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/x86_64-linux-gnu ../..
CMake Warning (dev) at CMakeLists.txt:45 (project):
[... snipped ...]
cp: cannot stat
'doxygen/d1/d34/class_m_s_device___taxi_a55128e31c22ec784b63868b846be485f_icgraph.dot':
No such file or directory
cp: cannot stat
'doxygen/d1/d34/class_m_s_device___taxi_a5af511d709988db03b5ed82549ae56d2_icgraph.dot':
No such file or directory
cp: cannot stat
'doxygen/d1/d34/class_m_s_device___taxi_a68427d7dc489bfff207d646f9af2617b_icgraph.dot':
No such file or directory
cp: cannot stat
'doxygen/d1/d34/class_m_s_device___taxi_a75efc29a0196691e5e12df7fe75409a8_icgraph.dot':
No such file or directory
cp: cannot stat
'doxygen/d1/d34/class_m_s_device___taxi_a7741fe7e3a561269ef42722397338e4f_icgraph.dot':
No such file or directory
cp: cannot stat
'doxygen/d1/d34/class_m_s_device___taxi_a8a8cde0d65f4e42ddd52aeca3b6102ec_icgraph.dot':
No such file or directory
cp: cannot stat
'doxygen/d1/d34/class_m_s_device___taxi_a92a4884c8b00bb5a1fc5a3e848e00543_icgraph.dot':
No such file or directory
cp: cannot stat
'doxygen/d1/d34/class_m_s_device___taxi_a92ddcdb70119189e54f71f3b092584d6_icgraph.dot':
No such file or directory
dh_installdocs: error: cd './docs/doxygen/..' && find 'doxygen' \( -type f -or -type l \)
-and ! -empty -print0 | LC_ALL=C sort -z | xargs -0 -I {} cp --reflink=auto --parents -dp {}
/<>/debian/sumo-doc/usr/share/doc/sumo returned exit code 123
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Full build log available here:
https://people.debian.org/~sanvila/build-logs/202409/
I'm using machines with 1 CPU and 2 CPUs from AWS.
- On machines with 1 CPU, this does not seem to happen (so far).
- On machines with 2 CPUs, this happens about 50% of the time
(tried 27 times so far, it failed 14 times).
The sumo package does not have an override for dh_installdocs in its
debian/rules,
so maybe this is debhelper's fault, but it could also be the case that this
line:
cd $(BUILDDIR) && $(MAKE) doxygen
produces a "tainted" tree which makes dh_installdocs to fail.
As always, I can create a VM for you to reproduce if it helps (please contact
me privately for that), with the logical caveat that it happens only 50% of the
time.
Please reassign & retitle as appropriate.
Thanks.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1081876: python-meshplex: FTBFS: FAILED tests/test_remove_cells.py::test_remove_cells_boundary - assert False
Package: src:python-meshplex Version: 0.17.1-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_meshplex * Building wheel... Successfully built meshplex-0.17.1-py3-none-any.whl I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with "installer" module debian/rules execute_after_dh_auto_build-indep make[1]: Entering directory '/<>' PYTHONPATH=.pybuild/cpython3_3.12_meshplex/build sphinx-build -M html docs/ .pybuild/docs Running Sphinx v7.4.7 loading translations [en]... done making output directory... done building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 1 source files that are out of date updating environment: [new config] 1 added, 0 changed, 0 removed reading sources... [100%] index looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done copying assets... copying static files... done copying extra files... done copying assets: done writing output... [100%] index generating indices... genindex py-modindex done writing additional pages... search done dumping search index in English (code: en)... done dumping object inventory... done build succeeded. The HTML pages are in .pybuild/docs/html. make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' MPLBACKEND=Agg dh_auto_test -- --test-args="--ignore-glob=*test_io*" I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_meshplex/build; python3.12 -m pytest --ignore-glob=*test_io* = test session starts == platform linux -- Python 3.12.6, pytest-8.3.2, pluggy-1.5.0 rootdir: /<>/.pybuild/cpython3_3.12_meshplex/build configfile: pyproject.toml plugins: typeguard-4.3.0 collected 112 items tests/mesh_tri/test_curl.py .[ 0%] tests/mesh_tri/test_edge_flip.py .. [ 13%] tests/mesh_tri/test_genus.py . [ 14%] tests/mesh_tri/test_mesh_tri.py .. [ 33%] tests/mesh_tri/test_plot.py .. [ 35%] tests/mesh_tri/test_remove_points.py . [ 36%] tests/test_ce_ratios.py [ 40%] tests/test_cell_partitions.py [ 43%] tests/test_circumcenters.py [ 47%] tests/test_compute_cell_values.py . [ 48%] tests/test_control_volume_centroids.py ... [ 50%] tests/test_control_volumes.py . [ 55%] tests/test_create_facets.py s... [ 58%] tests/test_degenerate.py [ 62%] tests/test_gh_issues.py .. [ 64%] tests/test_heights.py ...[ 66%] tests/test_mesh_line.py .[ 67%] tests/test_mesh_tetra.py .s [ 76%] tests/test_remove_cells.py F.. [ 86%] tests/test_signed_area.py [ 93%] tests/test_subdomain.py ... [ 96%] tests/test_volumes.py [100%] === FAILURES === __ test_remove_cells_boundary __ def test_remove_cells_boundary(): mesh = get_mesh1() assert np.all(mesh.is_boundary_point == [True, True, True, True, False]) assert np.all(mesh.is_boundary_facet_local[0] == [False, False, False, False]) assert np.all(mesh.is_boundary_facet_local[1] == [False, False, False, True]) assert np.all(mesh.is_boundary_facet_local[2] == [True, True, True, False]) assert np.all( mesh.is_boundary_facet == [True, True, False, True, False, True, False, False] ) assert np.all(mesh.is_boundary_cell) assert np.all(mesh.facets_cells_i
Bug#1081097: pytorch-sparse: FTBFS: unsatisfiable build-depends
Package: src:pytorch-sparse Version: 0.6.18-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-torch : Depends: python3 (< 3.12) but 3.12.5-1 is to be installed Depends: python3.11:any but it is not installable python3-torch-scatter : Depends: python3 (< 3.12) but 3.12.5-1 is to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202409/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1081105: tiemu: FTBFS: gencpu.c:307:13: error: type of ‘needcycles’ defaults to ‘int’ [-Wimplicit-int]
Package: src:tiemu Version: 3.04~git20220826.cda2db4+dfsg-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead dh_autoreconf Copying file po/Makevars.template acinclude.m4:2922: warning: the serial number must appear before any macro definition acinclude.m4:2967: warning: the serial number must appear before any macro definition acinclude.m4:3012: warning: the serial number must appear before any macro definition libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' acinclude.m4:2922: warning: the serial number must appear before any macro definition acinclude.m4:2967: warning: the serial number must appear before any macro definition acinclude.m4:3012: warning: the serial number must appear before any macro definition configure.ac:37: warning: The macro 'AC_LIBTOOL_WIN32_DLL' is obsolete. configure.ac:37: You should run autoupdate. m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from... configure.ac:37: the top level configure.ac:37: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and the call to _LT_SET_OPTION when you configure.ac:37: put the 'win32-dll' option into LT_INIT's first parameter. ./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from... m4/ltoptions.m4:148: AC_LIBTOOL_WIN32_DLL is expanded from... configure.ac:37: the top level configure.ac:38: warning: The macro 'AC_PROG_LIBTOOL' is obsolete. configure.ac:38: You should run autoupdate. m4/libtool.m4:100: AC_PROG_LIBTOOL is expanded from... configure.ac:38: the top level configure.ac:46: warning: The macro 'AC_ISC_POSIX' is obsolete. configure.ac:46: You should run autoupdate. ./lib/autoconf/specific.m4:732: AC_ISC_POSIX is expanded from... configure.ac:46: the top level configure.ac:52: warning: AM_PROG_MKDIR_P: this macro is deprecated, and will soon be removed. configure.ac:52: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead, configure.ac:52: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files. ./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from... aclocal.m4:1305: AM_PROG_MKDIR_P is expanded from... m4/po.m4:23: AM_PO_SUBDIRS is expanded from... m4/gettext.m4:57: AM_GNU_GETTEXT is expanded from... configure.ac:52: the top level configure.ac:52: warning: The macro 'AC_TRY_LINK' is obsolete. configure.ac:52: You should run autoupdate. ./lib/autoconf/general.m4:2918: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:697: AS_IF is expanded from... ./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from... m4/gettext.m4:365: gt_INTL_MACOSX is expanded from... m4/gettext.m4:57: AM_GNU_GETTEXT is expanded from... configure.ac:52: the top level configure.ac:52: warning: The macro 'AC_TRY_LINK' is obsolete. configure.ac:52: You should run autoupdate. ./lib/autoconf/general.m4:2918: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:697: AS_IF is expanded from... ./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from... m4/gettext.m4:57: AM_GNU_GETTEXT is expanded from... configure.ac:52: the top level configure.ac:52: warning: The macro 'AC_TRY_LINK' is obsolete. configure.ac:52: You should run autoupdate. ./lib/autoconf/general.m4:2918: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:697: AS_IF is expanded from... ./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from... m4/iconv.m4:20: AM_ICONV_LINK is expanded from... m4/gettext.m4:57: AM_GNU_GETTEXT is expanded from... configure.ac:52: the top level configure.ac:85: warning: The macro 'AC_HELP_STRING' is obsolete. configure.ac:85: You should run autoupdate. ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from... configure.ac:85: the top level configure.ac:152: warning: The macro 'AC_HELP_STRING' is obsolete. configure.ac:152: You should run autoupdate. ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from... configure.ac:152: the top level configure.ac:171: warning: The macro 'AC_HELP_STRING' is obsolet
Bug#1081084: nfft: FTBFS: sh: 1: latex: not found
Package: src:nfft
Version: 3.5.3-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:281: warning: The macro 'AC_PROG_CC_C99' is obsolete.
configure.ac:281: You should run autoupdate.
[... snipped ...]
../../tests/nfft.c:360:60: note: expected ‘init_delegate_t **’ {aka ‘struct
init_delegate_s **’} but argument is of type ‘const init_delegate_t **’ {aka
‘const struct init_delegate_s **’}
360 | const testcase_delegate_t **testcases, init_delegate_t **initializers,
| ~~^~~~
../../tests/nfct.c:956:26: error: passing argument 5 of ‘check_many’ from
incompatible pointer type [-Wincompatible-pointer-types]
956 | testcases_1d_online, initializers_1d, &check_trafo,
trafos_1d_online);
| ^~~
| |
| const init_delegate_t ** {aka const struct
init_delegate_s **}
../../tests/nfct.c:359:60: note: expected ‘init_delegate_t **’ {aka ‘struct
init_delegate_s **’} but argument is of type ‘const init_delegate_t **’ {aka
‘const struct init_delegate_s **’}
359 | const testcase_delegate_t **testcases, init_delegate_t **initializers,
| ~~^~~~
../../tests/nfct.c:956:57: error: passing argument 7 of ‘check_many’ from
incompatible pointer type [-Wincompatible-pointer-types]
956 | testcases_1d_online, initializers_1d, &check_trafo,
trafos_1d_online);
| ^~~~
| |
| const
trafo_delegate_t ** {aka const struct trafo_delegate_s **}
../../tests/nfct.c:360:56: note: expected ‘trafo_delegate_t **’ {aka ‘struct
trafo_delegate_s **’} but argument is of type ‘const trafo_delegate_t **’ {aka
‘const struct trafo_delegate_s **’}
360 | check_delegate_t *check_delegate, trafo_delegate_t **trafos)
| ~~~^~
../../tests/nfct.c: In function ‘nfctl_check_adjoint_1d_online’:
../../tests/nfft.c:1176:67: error: passing argument 7 of ‘check_many’ from
incompatible pointer type [-Wincompatible-pointer-types]
1176 | testcases_adjoint_2d_online, initializers_2d, &check_adjoint,
trafos_adjoint_2d_online);
|
^~~~
| |
| const
trafo_delegate_t ** {aka const struct trafo_delegate_s **}
../../tests/nfct.c:987:5: error: passing argument 4 of ‘check_many’ from
incompatible pointer type [-Wincompatible-pointer-types]
987 | testcases_adjoint_1d_online, initializers_1d, &check_adjoint,
trafos_adjoint_1d_online);
| ^~~
| |
| const testcase_delegate_online_t ** {aka const struct
testcase_delegate_online_s **}
../../tests/nfct.c:359:31: note: expected ‘const testcase_delegate_t **’ {aka
‘const struct testcase_delegate_s **’} but argument is of type ‘const
testcase_delegate_online_t **’ {aka ‘const struct testcase_delegate_online_s
**’}
359 | const testcase_delegate_t **testcases, init_delegate_t **initializers,
| ^
../../tests/nfct.c:987:34: error: passing argument 5 of ‘check_many’ from
incompatible pointer type [-Wincompatible-pointer-types]
987 | testcases_adjoint_1d_online, initializers_1d, &check_adjoint,
trafos_adjoint_1d_online);
| ^~~
| |
| const init_delegate_t ** {aka const
struct init_delegate_s **}
../../tests/nfct.c:359:60: note: expected ‘init_delegate_t **’ {aka ‘struct
init_delegate_s **’} but argument is of type ‘const init_delegate_t **’ {aka
‘const struct init_delegate_s **’}
359 | const testcase_delegate_t **testcases, init_delegate_t **initializers,
| ~~^~~~
../../tests/nfft.c:361:56: note: expected ‘trafo_delegate_t **’ {aka ‘struct
Bug#1081096: pytorch-scatter: FTBFS: unsatisfiable build-depends
Package: src:pytorch-scatter Version: 2.1.2-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-torch : Depends: python3 (< 3.12) but 3.12.5-1 is to be installed Depends: python3.11:any but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202409/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1081095: pytorch-ignite: FTBFS: unsatisfiable build-depends
Package: src:pytorch-ignite Version: 0.4.12-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-torch : Depends: python3 (< 3.12) but 3.12.5-1 is to be installed Depends: python3.11:any but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202409/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1081094: pytorch-cluster: FTBFS: unsatisfiable build-depends
Package: src:pytorch-cluster Version: 1.6.3-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-torch : Depends: python3 (< 3.12) but 3.12.5-1 is to be installed Depends: python3.11:any but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202409/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1081088: open3d: FTBFS: unsatisfiable build-depends
Package: src:open3d Version: 0.18.0+ds-3.1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-torch : Depends: python3 (< 3.12) but 3.12.5-1 is to be installed Depends: python3.11:any but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202409/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1081052: adios: FTBFS: mpi-compat.h:7:10: fatal error: mpi.h: No such file or directory
Package: src:adios
Version: 1.13.1-37
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
dh_update_autotools_config
cp -an --reflink=auto config/config.guess
debian/.debhelper/bucket/files/3dfc63c81063ba5edeb599dc48f958e2e4c4759c968d012a4095e53441af7c1d.tmp
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
mv
debian/.debhelper/bucket/files/3dfc63c81063ba5edeb599dc48f958e2e4c4759c968d012a4095e53441af7c1d.tmp
debian/.debhelper/bucket/files/3dfc63c81063ba5edeb599dc48f958e2e4c4759c968d012a4095e53441af7c1d
cp -f /usr/share/misc/config.guess ./config/config.guess
cp -an --reflink=auto config/config.sub
debian/.debhelper/bucket/files/52d7418817df4a0bd139446cf014f9dfd5bb3406a95c3109ca6fd578068be472.tmp
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
mv
debian/.debhelper/bucket/files/52d7418817df4a0bd139446cf014f9dfd5bb3406a95c3109ca6fd578068be472.tmp
debian/.debhelper/bucket/files/52d7418817df4a0bd139446cf014f9dfd5bb3406a95c3109ca6fd578068be472
cp -f /usr/share/misc/config.sub ./config/config.sub
dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec md5sum {} + -o
-type l -printf "symlink %p
" > debian/autoreconf.before
[... snipped ...]
Making all in global-array-time
make[6]: Entering directory
'/<>/build-openmpi/examples/C/global-array-time'
mpicc.openmpi -DHAVE_CONFIG_H -I. -I../../../../examples/C/global-array-time -I../../..
-I../../../src/public -I../../../../src -I../../../../src/public -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 -fcf-protection -fPIC -c -o
adios_globaltime.o ../../../../examples/C/global-array-time/adios_globaltime.c
mpicc.openmpi -DHAVE_CONFIG_H -I. -I../../../../examples/C/global-array-time -I../../..
-I../../../src/public -I../../../../src -I../../../../src/public -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 -fcf-protection -fPIC -c -o
adios_globaltime_no_xml.o ../../../../examples/C/global-array-time/adios_globaltime_no_xml.c
mpicc.openmpi -DHAVE_CONFIG_H -I. -I../../../../examples/C/global-array-time -I../../..
-I../../../src/public -I../../../../src -I../../../../src/public -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 -fcf-protection -fPIC -c -o
adios_read_globaltime.o ../../../../examples/C/global-array-time/adios_read_globaltime.c
mpicc.openmpi -DHAVE_CONFIG_H -I. -I../../../../examples/C/global-array-time -I../../..
-I../../../src/public -I../../../../src -I../../../../src/public -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 -fcf-protection -fPIC -c -o
adios_read_globaltime_streaming.o
../../../../examples/C/global-array-time/adios_read_globaltime_streaming.c
test "../../../../examples/C/global-array-time" = "." || cp
../../../../examples/C/global-array-time/*.xml .
/bin/bash ../../../libtool --tag=CC --mode=link mpicc.openmpi -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection -fPIC -L/usr/lib/x86_64-linux-gnu/netcdf/mpi
-L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -L/usr/lib64 -L/usr/lib -L/usr/lib -L/usr/lib64
-L/usr/lib64 -L/usr/lib -L/usr/lib -L/usr/lib -Wl,-z,relro -o adios_globaltime
adios_globaltime.o ../../../src/libadios.a -lnetcdf -lhdf5_hl -lhdf5 -lz -libverbs
-lglib-2.0 -lz -lbz2 -lsz -llz4 -lblosc -lm -lpthread
/bin/bash ../../../libtool --tag=CC --mode=link mpicc.openmpi -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection -fPIC -L/usr/lib/x86_64-linux-gnu/netcdf/mpi
-L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -L/usr/lib64 -L/usr/lib -L/usr/lib -L/usr/lib64
-L/usr/lib64 -L/usr/lib -L/usr/lib -L/usr/lib -Wl,-z,relro -o adios_globaltime_no_xml
adios_globaltime_no_xml.o ../../../src/libadios.a -lnetcdf -lhdf5_hl -lhdf5 -lz -libverbs
-lglib-2.0 -lz -lbz2 -lsz -llz4 -lblosc -lm -lpthread
libtool: link: mpicc.openmpi -g -O2 -Werror=implicit-function-declaration
-ffile-pr
Bug#1080123: pycollada: FTBFS: FAIL: test_cimage_data_loading (collada.tests.test_material.TestMaterial.test_cimage_data_loading)
Package: src:pycollada Version: 0.7.2-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --buildsystem=pybuild --with python3 dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) running config dh_auto_build -O--buildsystem=pybuild 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 creating /<>/.pybuild/cpython3_3.12/build/collada copying collada/lineset.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/primitive.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/polylist.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/material.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/source.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/scene.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/xmlutil.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/controller.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/geometry.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/__init__.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/polygons.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/animation.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/common.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/util.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/triangleset.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/camera.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/light.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/schema.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/__main__.py -> /<>/.pybuild/cpython3_3.12/build/collada copying collada/asset.py -> /<>/.pybuild/cpython3_3.12/build/collada creating /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_asset.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_lineset.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_light.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_iteration.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_geometry.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_collada.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/__init__.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_source.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_material.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_camera.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests copying collada/tests/test_scene.py -> /<>/.pybuild/cpython3_3.12/build/collada/tests creating /<>/.pybuild/cpython3_3.12/build/collada/resources copying collada/resources/schema-1.4.1.xml -> /<>/.pybuild/cpython3_3.12/build/collada/resources copying collada/resources/xsd.xml -> /<>/.pybuild/cpython3_3.12/build/collada/resources dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build; python3.12 -m unittest discover -v test_asset (collada.tests.test_asset.TestAsset.test_asset) ... ok test_asset_contributor (collada.tests.test_asset.TestAsset.test_asset_contributor) ... ok test_orthographic_camera_saving (collada.tests.test_camera.TestCamera.test_orthographic_camera_saving) ... ok test_orthographic_camera_xmag_ymag_aspect_ratio (collada.tests.test_camera.TestCamera.test_orthographic_camera_xmag_ymag_aspect_ratio) ... ok test_perspective_camera_saving (collada.tests.test_camera.TestCamera.test_perspective_camera_saving) ... ok test_perspective_camera_xfov_yfov_aspect_ratio (collada.tests.test_camera.TestCamera.test_perspective_camera_xfov_yfov_aspect_ratio) ... ok test_collada_attribute_replace (collada.tests.test_collada.TestCollada.test_collada_attribute_replace) ... ok test_collada_duck_poly (collada.tests.test_collada.TestCollada.test_collada_duck_poly) ... ERROR test_collada_duck_tris (collada.tests.test_collada.TestCollada.test_collada_duck_tris) ... ERROR test_collada_duck_zip (collada.tests.test_collada.TestCollada.test_collada_duck_zip) ... ERROR test_collada_empty_triangles (collada.tests.test_collada.TestCollada.test_collada_empty_triangles
Bug#1076901: opencv: diff for NMU version 4.6.0+dfsg-13.2
El 16/8/24 a las 1:12, p...@debian.org escribió: I'm sorry I had your message too late. The delayed upload was accepted already. No problem. You uploaded -13.2 to delayed, I uploaded -14 this afternoon. Your upload was accepted by the upload queue, but not by dinstall, who will probably reject it when it checks that 13.2(yours) < 14(unstable) This is why I said "or just let it fail" (i.e. do nothing). At this point it does not really matter, so don't worry. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1076901: opencv: diff for NMU version 4.6.0+dfsg-13.2
Hi. I'm going to make a team upload including your changes. I hope the usual uploaders do not mind. Otherwise, this would be the second NMU which is not synced to salsa, and this is becoming a little bit messy, imo. I guess you may cancel your NMU (or just let it fail). Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1078288: loki-ecmwf: FTBFS: Handler for event 'html-page-context' threw an exception (exception: maximum recursion depth exceeded)
Package: src:loki-ecmwf Version: 0.2.3-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --buildsystem=pybuild --with python3,sphinxdoc dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure (cd loki; ln -s ../scripts ) make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' PYBUILD_NAME=loki-ecmwf dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_loki-ecmwf [... snipped ...] * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.scheduler.SFilter. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.configure.SchedulerConfig. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.configure.TransformationConfig. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.configure.ItemConfig. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.item.Item. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.item.FileItem. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.item.ModuleItem. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.item.ProcedureItem. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.item.TypeDefItem. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.item.ProcedureBindingItem. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.item.InterfaceItem. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/transform.rst:282: WARNING: autosummary: failed to import loki.bulk.item.ItemFactory. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:34: WARNING: autosummary: failed to import loki.pragma_utils.is_loki_pragma. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:34: WARNING: autosummary: failed to import loki.pragma_utils.get_pragma_parameters. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:34: WARNING: autosummary: failed to import loki.pragma_utils.pragmas_attached. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:34: WARNING: autosummary: failed to import loki.pragma_utils.pragma_regions_attached. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:50: WARNING: autosummary: failed to import loki.analyse.analyse_dataflow.dataflow_analysis_attached. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:62: WARNING: autosummary: failed to import loki.dimension.Dimension. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:73: WARNING: autosummary: failed to import loki.tools.files. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:73: WARNING: autosummary: failed to import loki.tools.strings. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:73: WARNING: autosummary: failed to import loki.tools.util. Possible hints: * KeyError: 'loki' * ModuleNotFoundError: No module named 'pcpp' /<>/docs/source/utils.rst:96: WARNING: autosummary: failed to import loki.logging. Possible hints: * Ke
Bug#1003395: plfit: under-the-radar numerical issue
tags 1003395 - ftbfs tags 1003395 - patch thanks El 3/8/24 a las 23:31, Jerome BENOIT escribió: I am re-opening the issue because it has simply gone under the radar but it is still there. The issue is a numerical issue that deserves an appropriate numerical analysis. The upstream code currently workarounds by using at some point `long double`. This is a very bad numerical practice: all the computation must be made with `double`. The issue is actually not numerically trivial. I am on my way to elaborate a numerical fix. Ok, I would have used a different bug for that myself, but if you want to use the same bug for the underlying issue, so be it. Note, however, that the original report said the package FTBFS, which does not happen anymore, and it had a patch from Ubuntu which will probably not be applied, so I hope you don't mind if I adjust the metadata accordingly. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1077953: z88: FTBFS: src/z88ai.c:208:57: error: passing argument 4 of ‘qsort’ from incompatible pointer type
Package: src:z88 Version: 13.0.0+dfsg2-7 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --sourcedirectory=src --buildsystem=cmake dh_update_autotools_config -O--sourcedirectory=src -O--buildsystem=cmake dh_autoreconf -O--sourcedirectory=src -O--buildsystem=cmake debian/rules override_dh_auto_configure-arch make[1]: Entering directory '/<>' dh_auto_configure -- -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_SHARED_LINKER_FLAGS="-Wl,--as-needed" -DCMAKE_EXE_LINKER_FLAGS="-Wl,--as-needed" -DCMAKE_SKIP_RPATH:BOOL=ON -DCMAKE_BUILD_TYPE="Release" cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb 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/x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_SHARED_LINKER_FLAGS=-Wl,--as-needed -DCMAKE_EXE_LINKER_FLAGS=-Wl,--as-needed -DCMAKE_SKIP_RPATH:BOOL=ON -DCMAKE_BUILD_TYPE=Release ../src CMake Deprecation Warning at CMakeLists.txt:4 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. [... snipped ...] CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/dyn88o.c This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/wlog88o.c This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/ale88o.c This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/rcoo88.c This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/m9.c This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/m10.c This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/m12.c This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/m15.c This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:87 (add_executable): Policy CMP0115 is not set: Source file extensions must be explicit. Run "cmake --help-policy CMP0115" for policy details. Use the cmake_policy command to set the policy and suppress this warning. File: /<>/src/oc88.c This warning is for project developer
Bug#1077852: plfit-doc contains a /CONTRIBUTORS.txt
tags 1077852 + patch thanks El 3/8/24 a las 14:24, Jochen Sprickerhof escribió: the plfit-doc contains a CONTRIBUTORS.txt in the root directory. I guess it should be in /usr/share/doc/plfit/ or somewhere. Big oops! I'm surprised that ftpmasters do not have a lintian check to reject something like that. Maybe file-in-unusual-directory is too weak and we need another check like file-in-root-directory. Anyway, trivial patch attached. Jerome: I leave this to you, since you are the usual uploader, but if you prefer, I could fix this via Team Upload. Thanks. diff --git a/debian/plfit-doc.install b/debian/plfit-doc.install index 30493f8..2231586 100644 --- a/debian/plfit-doc.install +++ b/debian/plfit-doc.install @@ -1,4 +1,4 @@ test/*.h test/*.c debian/adhoc/examples/tests/* usr/share/doc/plfit/examples/tests test/*.py debian/adhoc/examples/pytests/* usr/share/doc/plfit/examples/pytests doc/THANKS usr/share/doc/plfit -CONTRIBUTORS.txt +CONTRIBUTORS.txt usr/share/doc/plfit -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1003395: plfit FTBFS on s390x
close 1003395 0.9.5+ds-1
thanks
Hello.
This was fixed upstream and there is apparently no need to apply
any patch anymore.
I've written the long explanation in the github issue:
https://github.com/ntamas/plfit/issues/38
TLDR: It was fixed by the line in src/CMakeLists.txt saying this:
target_link_libraries(plfit ${MATH_LIBRARY})
Cc:ing all relevant parties.
Thanks.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1076923: scikit-learn: FTBFS: dh_sphinxdoc: error: debian/python-sklearn-doc/usr/share/doc/python-sklearn-doc/html/search.html does not load searchindex.js
Package: src:scikit-learn Version: 1.4.2+dfsg-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with sphinxdoc --buildsystem pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' mkdir -p tmp mv PKG-INFO PKG-INFO-BAK python3.12 setup.py config Partial import of sklearn during the build process. Compiling sklearn/__check_build/_check_build.pyx because it changed. Compiling sklearn/_isotonic.pyx because it changed. Compiling sklearn/_loss/_loss.pyx because it changed. Compiling sklearn/cluster/_dbscan_inner.pyx because it changed. [... snipped ...] byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/_packaging/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/_packaging/_structures.py to _structures.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/_scipy/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/_scipy/sparse/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/_scipy/sparse/csgraph/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/_scipy/sparse/csgraph/_laplacian.py to _laplacian.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/_arff.py to _arff.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/externals/conftest.py to conftest.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/_hash.py to _hash.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/text.py to text.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/tests/test_dict_vectorizer.py to test_dict_vectorizer.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/tests/test_image.py to test_image.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/tests/test_feature_hasher.py to test_feature_hasher.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/tests/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/tests/test_text.py to test_text.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/_dict_vectorizer.py to _dict_vectorizer.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/image.py to image.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/feature_extraction/_stop_words.py to _stop_words.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/_build_utils/version.py to version.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/_build_utils/pre_build_helpers.py to pre_build_helpers.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/_build_utils/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/_build_utils/openmp_helpers.py to openmp_helpers.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/_build_utils/tempita.py to tempita.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/naive_bayes.py to naive_bayes.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/conftest.py to conftest.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/impute/_iterative.py to _iterative.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/impute/__init__.py to __init__.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/impute/_base.py to _base.cpython-312.pyc byte-compiling /<>/debian/tmp/usr/lib/python3.12/dist-packages/sklearn/impute/tests/test_impute.py to test_impute.cpython-312.pyc byte-co
Bug#1076901: opencv: FTBFS: configure error
Package: src:opencv Version: 4.6.0+dfsg-13.1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' # prepare the 3rd party directory test -d 3rdparty || cp -av debian/3rdparty-4.6.0 3rdparty 'debian/3rdparty-4.6.0' -> '3rdparty' 'debian/3rdparty-4.6.0/quirc' -> '3rdparty/quirc' 'debian/3rdparty-4.6.0/quirc/CMakeLists.txt' -> '3rdparty/quirc/CMakeLists.txt' 'debian/3rdparty-4.6.0/quirc/LICENSE' -> '3rdparty/quirc/LICENSE' 'debian/3rdparty-4.6.0/quirc/include' -> '3rdparty/quirc/include' 'debian/3rdparty-4.6.0/quirc/include/quirc.h' -> '3rdparty/quirc/include/quirc.h' [... snipped ...] //Choose the type of build, options are: None Debug Release RelWithDebInfo // MinSizeRel ... CMAKE_BUILD_TYPE:STRING=None //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-13 //A wrapper around 'ranlib' adding the appropriate '--plugin' option // for the GCC compiler CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-13 //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 -fcf-protection -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-13 //A wrapper around 'ranlib' adding the appropriate '--plugin' option // for the GCC compiler CMAKE_C_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-13 //Flags used by the C compiler during all build types. CMAKE_C_FLAGS:STRING=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 //Flags used by the C compiler during DEBUG builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the C compiler during MINSIZEREL builds. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the C compiler during NONE builds. CMAKE_C_FLAGS_NONE:STRING= //Flags used by the C compiler during RELEASE builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the C compiler during RELWITHDEBINFO builds. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Path to a program. CMAKE_DLLTOOL:FILEPATH=CMAKE_DLLTOOL-NOTFOUND //Flags used by the linker during all build types. CMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-z,relro -Wl,-z,now //Flags used by the linker during DEBUG builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during MINSIZEREL builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during NONE builds. CMAKE_EXE_LINKER_FLAGS_NONE:STRING= //Flags used by the linker during RELEASE builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during RELWITHDEBINFO builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL= //No help, variable specified on the command line. CMAKE_EXPORT_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON //No help, variable specified on the command line. CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON //Value Computed by CMake. CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=/<>/.pybuild/cpython3_3.12_opencv/build/CMakeFiles/pkgRedirects //No help, variable specified on the command line. CMAKE_FIND_USE_PACKAGE_REGISTRY:UNINITIALIZED=OFF //No help, variable specified on the command line. CMAKE_INSTALL_LIBDIR:UNINITIALIZED=lib/x86_64-linux-gnu //No help, variable specified on the command line. CMAKE_INSTALL_LOCALSTATEDIR:UNINITIALIZED=/var //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/usr //No help, variable specified on the command line. CMAKE_INSTALL_RUNSTATEDIR:UNINITIALIZED=/run //No help, variable specified on the command line. CMAKE_INSTALL_SYSCONFDIR:UNINITIALIZED=/etc //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Program used to build from build.ninja files. CMAKE_MA
Bug#1071722: adios4dolfinx: FTBFS: failing tests
El 31/5/24 a las 13:21, Drew Parsons escribió: Source: adios4dolfinx Followup-For: Bug #1071722 Santiago, could you try running with export OMPI_MCA_rmaps_base_oversubscribe=true added to the top of debian/rules? That seems to work. And also it works again on single-cpu systems (where it previously also failed). But if the user sets DEB_BUILD_OPTIONS=parallel=1 and the package oversubscribes anyway, then we would not honoring DEB_BUILD_OPTIONS and it would still be a bug (admittedly, less severe than a FTBFS bug). (p.s. please always Cc:me in the BTS, messages are very easy to miss). Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1072138: python-peachpy: FTBFS: dh_sphinxdoc: error: debian/python-peachpy-doc/usr/share/doc/python3-peachpy/html/_static/bootstrap-3.4.1/js/bootstrap.min.js is missing
Package: src:python-peachpy Version: 0.0~git20211013.257881e-1.1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with python3,sphinxdoc --buildsystem pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.11 setup.py config /usr/lib/python3/dist-packages/setuptools/__init__.py:84: _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`. [... snipped ...] runTest (test.x86_64.encoding.test_mmxsse.TestPCMPISTRM.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPEXTRB.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPEXTRD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPEXTRQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPEXTRW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPHADDD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPHADDSW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPHADDW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPHMINPOSUW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPHSUBD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPHSUBSW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPHSUBW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPINSRB.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPINSRD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPINSRQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPINSRW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMADDUBSW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMADDWD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMAXSB.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMAXSD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMAXSW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMAXUB.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMAXUD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMAXUW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMINSB.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMINSD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMINSW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMINUB.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMINUD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMINUW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVMSKB.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVSXBD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVSXBQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVSXBW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVSXDQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVSXWD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVSXWQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVZXBD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVZXBQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVZXBW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVZXDQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVZXWD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMOVZXWQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMULDQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMULHRSW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMULHUW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMULHW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMULLD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMULLW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPMULUDQ.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPOR.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPSADBW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPSHUFB.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPSHUFD.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPSHUFHW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPSHUFLW.runTest) ... ok runTest (test.x86_64.encoding.test_mmxsse.TestPSHUFW.runTest) ... ok
Bug#1071722: adios4dolfinx: FTBFS: failing tests
In such bug I proposed to run mpi with true and skip the tests if it fails. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057556#34 Maybe a similar idea would work here as well. We can try that. As you suggested in the other bug, it might be quirk of openmpi we're facing. openmpi distinguishs sockets, cores, slots, hwthread. On one system two cores might be found in one socket, on another each core might have its own socket. To track that, what does `lscpu` report on your failing system? (the thread,core,socket lines are probably the relevant ones) It's an AWS machine of type m6a.large. These are the most relevant specs. Thread(s) per core: 2 Core(s) per socket: 1 Socket(s):1 (full lscpu attached in case it matters) So it seems to have "one core, two threads". I can try changing the n=2 parameter in the ipp.Cluster invocation to n=1 and tell you if there is any change, if it helps. I don't think that will make things worse in any case. Thanks.Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes:48 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID:AuthenticAMD BIOS Vendor ID: Advanced Micro Devices, Inc. Model name: AMD EPYC 7R13 Processor BIOS Model name: AMD EPYC 7R13 Processor CPU @ 2.6GHz BIOS CPU family: 107 CPU family: 25 Model:1 Thread(s) per core: 2 Core(s) per socket: 1 Socket(s):1 Stepping: 1 BogoMIPS: 5299,99 Flags:fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch topoext invpcid_single ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 clzero xsaveerptr rdpru wbnoinvd arat npt nrip_save vaes vpclmulqdq rdpid Hypervisor vendor:KVM Virtualization type: full L1d cache:32 KiB (1 instance) L1i cache:32 KiB (1 instance) L2 cache: 512 KiB (1 instance) L3 cache: 4 MiB (1 instance) NUMA node(s): 1 NUMA node0 CPU(s):0,1 Vulnerability Gather data sampling: Not affected Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds:Not affected Vulnerability Meltdown: Not affected Vulnerability Mmio stale data:Not affected Vulnerability Reg file data sampling: Not affected Vulnerability Retbleed: Not affected Vulnerability Spec rstack overflow: Mitigation; safe RET, no microcode Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Retpolines; IBPB conditional; IBRS_FW; STIBP always-on; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected Vulnerability Srbds: Not affected Vulnerability Tsx async abort:Not affected -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1071722: adios4dolfinx: FTBFS: failing tests
El 25/5/24 a las 16:42, Drew Parsons escribió: Source: adios4dolfinx Followup-For: Bug #1071722 Control: tags -1 ftbfs adios4dolfinx is building cleanly in reproducibility builds. Perhaps the problem was a temporary glitch on your test system? No, this is unlikely to be a temporary glitch: Status: successful adios4dolfinx_0.7.3-1_amd64-20240215T153414.310Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240504T105910.601Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240504T105911.782Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240504T105926.289Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240504T105927.312Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240508T222341.343Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240508T230025.295Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240520T162738.912Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240524T093906.909Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240524T093908.800Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240524T093910.225Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240524T095911.253Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240524T095911.177Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240524T100100.391Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240524T100158.350Z Status: failed adios4dolfinx_0.8.1.post0-1_amd64-20240525T133854.167Z My system has 2 CPUs, apparently MPI counts them as "one engine" and fails because the code has things like this: ipp.Cluster(engines="mpi", n=2) This bypasses whatever BUILD_OPTIONS=parallel=n setting the user might set. BTW: This bug looks similar to #1057556, which the maintainer misdiagnosed as "fails with a single cpu" (not true!). In such bug I proposed to run mpi with true and skip the tests if it fails. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057556#34 Maybe a similar idea would work here as well. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1071814: tpot: FTBFS: ERROR: Failure: AttributeError (module 'numpy' has no attribute 'float'.
Package: src:tpot Version: 0.11.7+dfsg-5 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with python3,mkdocs --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config running config I: pybuild base:311: python3.11 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build I: pybuild base:311: /usr/bin/python3.12 setup.py build running build [... snipped ...] The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in loadTestsFromName module = self.importer.importFromPath( ^ File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.11/imp.py", line 235, in load_module return load_source(name, filename, file) ^ File "/usr/lib/python3.11/imp.py", line 172, in load_source module = _load(spec) ^^^ File "", line 721, in _load File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "/<>/.pybuild/cpython3_3.11_tpot/build/tests/feature_transformers_tests.py", line 2, in from tpot.builtins import CategoricalSelector, ContinuousSelector File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/__init__.py", line 27, in from .tpot import TPOTClassifier, TPOTRegressor File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/tpot.py", line 31, in from .base import TPOTBase File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/base.py", line 68, in from .builtins import CombineDFs, StackingEstimator File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/builtins/__init__.py", line 29, in from .one_hot_encoder import OneHotEncoder, auto_select_categorical_features, _transform_selected File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/builtins/one_hot_encoder.py", line 136, in class OneHotEncoder(BaseEstimator, TransformerMixin): File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/builtins/one_hot_encoder.py", line 216, in OneHotEncoder def __init__(self, categorical_features='auto', dtype=np.float, File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 324, in __getattr__ raise AttributeError(__former_attrs__[attr]) AttributeError: module 'numpy' has no attribute 'float'. `np.float` was a deprecated alias for the builtin `float`. To avoid this error in existing code, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here. The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations == ERROR: Failure: ImportError ( `load_boston` has been removed from scikit-learn since version 1.2. The Boston housing prices dataset has an ethical problem: as investigated in [1], the authors of this dataset engineered a non-invertible variable "B" assuming that racial self-segregation had a positive impact on house prices [2]. Furthermore the goal of the research that led to the creation of this dataset was to study the impact of air quality but it did not give adequate demonstration of the validity of this assumption. The scikit-learn maintainers therefore strongly discourage the use of this dataset unless the purpose of the code is to study and educate about ethical issues in data science and machine learning. In this special case, you can fetch the dataset from the original source:: import pandas as pd import numpy as np data_url = "http://lib.stat.cmu.edu/datasets/boston"; raw_df = pd.read_csv(data_url, sep="\s+", skiprows=22, header=None) data = np.hstack([raw_df.va
Bug#1071813: spyder-memory-profiler: FTBFS: E ImportError: cannot import name 'get_icon' from 'spyder.utils.qthelpers' (/usr/lib/python3/dist-packages/spyder/utils/qthelpers.py)
Package: src:spyder-memory-profiler Version: 0.2.1-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config running config I: pybuild base:311: python3.11 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3.12 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler copying spyder_memory_profiler/memoryprofiler.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler copying spyder_memory_profiler/__init__.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler creating /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example copying spyder_memory_profiler/example/profiling_test_script.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example copying spyder_memory_profiler/example/__init__.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example creating /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data copying spyder_memory_profiler/data/__init__.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data creating /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets copying spyder_memory_profiler/widgets/memoryprofiler.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets copying spyder_memory_profiler/widgets/__init__.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets creating /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir copying spyder_memory_profiler/example/subdir/profiling_test_script2.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir copying spyder_memory_profiler/example/subdir/__init__.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir creating /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images copying spyder_memory_profiler/data/images/__init__.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images creating /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests copying spyder_memory_profiler/widgets/tests/test_memoryprofiler.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests copying spyder_memory_profiler/widgets/tests/__init__.py -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests copying spyder_memory_profiler/data/images/spyder.memory_profiler.png -> /<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler copying spyder_memory_profiler/memoryprofiler.py -> /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler copying spyder_memory_profiler/__init__.py -> /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler creating /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example copying spyder_memory_profiler/example/profiling_test_script.py -> /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example copying spyder_memory_profiler/example/__init__.py -> /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example creating /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/data copying spyder_memory_profiler/data/__init__.py -> /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/data creating /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/widgets copying spyder_memory_profiler/widgets/memoryprofiler.py -> /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/widgets copying spyder_memory_profiler/widgets/__init__.py -> /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/widgets creating /<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir copying spyder_memory_profiler/example/subdir/profiling_test_script2.py -> /<>/.pybuild/cpython3_3.11_spyder-memor
Bug#1071812: qiskit-ibmq-provider: FTBFS: E AttributeError: module 'numpy' has no attribute 'float'.
Package: src:qiskit-ibmq-provider Version: 0.4.6-4 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config running config I: pybuild base:311: python3.11 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3.12 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.12_qiskit-ibmq-provider/build/qiskit [... snipped ...] raise AttributeError(__former_attrs__[attr]) E AttributeError: module 'numpy' has no attribute 'float'. E `np.float` was a deprecated alias for the builtin `float`. To avoid this error in existing code, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here. E The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at: E https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations. Did you mean: 'cfloat'? _ ERROR collecting .pybuild/cpython3_3.12_qiskit-ibmq-provider/build/test/ibmq/test_registration.py _ test/ibmq/test_registration.py:27: in from qiskit.providers.ibmq import IBMQ, IBMQFactory /usr/lib/python3/dist-packages/qiskit/__init__.py:31: in from qiskit.circuit import ClassicalRegister /usr/lib/python3/dist-packages/qiskit/circuit/__init__.py:58: in from .quantumcircuit import QuantumCircuit /usr/lib/python3/dist-packages/qiskit/circuit/quantumcircuit.py:24: in from qiskit.circuit.instruction import Instruction /usr/lib/python3/dist-packages/qiskit/circuit/instruction.py:45: in from qiskit.qobj.models.qasm import QasmQobjInstruction /usr/lib/python3/dist-packages/qiskit/qobj/models/qasm.py:20: in from qiskit.validation.fields import List, Integer, InstructionParameter, Nested /usr/lib/python3/dist-packages/qiskit/validation/fields/__init__.py:43: in from .custom import Complex, InstructionParameter, DictParameters /usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:61: in class InstructionParameter(ModelTypeValidator): /usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:76: in InstructionParameter numpy.integer, numpy.float, /usr/lib/python3/dist-packages/numpy/__init__.py:324: in __getattr__ raise AttributeError(__former_attrs__[attr]) E AttributeError: module 'numpy' has no attribute 'float'. E `np.float` was a deprecated alias for the builtin `float`. To avoid this error in existing code, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here. E The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at: E https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations. Did you mean: 'cfloat'? _ ERROR collecting .pybuild/cpython3_3.12_qiskit-ibmq-provider/build/test/ibmq/websocket/test_websocket_integration.py _ test/ibmq/websocket/test_websocket_integration.py:21: in from qiskit import ClassicalRegister, QuantumCircuit, QuantumRegister /usr/lib/python3/dist-packages/qiskit/__init__.py:31: in from qiskit.circuit import ClassicalRegister /usr/lib/python3/dist-packages/qiskit/circuit/__init__.py:58: in from .quantumcircuit import QuantumCircuit /usr/lib/python3/dist-packages/qiskit/circuit/quantumcircuit.py:24: in from qiskit.circuit.instruction import Instruction /usr/lib/python3/dist-packages/qiskit/circuit/instruction.py:45: in from qiskit.qobj.models.qasm import QasmQobjInstruction /usr/lib/python3/dist-packages/qiskit/qobj/models/qasm.py:20: in from qiskit.validation.fields import List, Integer, InstructionParameter, Nested /usr/lib/python3/dist-packages/qiskit/validation/fields/__init__.py:43: in from .custom import Complex, InstructionParameter, DictParameters /usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:61: in class InstructionParameter(ModelTypeValidator): /usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:76: in InstructionParameter numpy.integer, numpy.float, /usr/lib/python3/dist-packages/numpy/__init__.py:324: in __getattr__ raise AttributeError(__former_attrs__[attr]) E AttributeError: module 'numpy' has no attribute 'float'. E `np.float` was a deprecated alias for the builtin `float`. To avoid this error in existing code, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here.
Bug#1071810: pyfftw: FTBFS: /tmp/pyfftw-l6u29tyw/fftw_plan_dft.c:2:17: error: implicit declaration of function ‘fftw_plan_dft’
Package: src:pyfftw Version: 0.13.1-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with sphinxdoc --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild pybuild:308: find -name "*.c" -delete I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_pyfftw * Building wheel... :46: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html /<>/versioneer.py:421: SyntaxWarning: invalid escape sequence '\s' LONG_VERSION_PY['git'] = ''' INFO:root:running bdist_wheel INFO:root:running build INFO:root:running build_py INFO:root:creating build INFO:root:creating build/lib.linux-x86_64-cpython-312 INFO:root:creating build/lib.linux-x86_64-cpython-312/pyfftw INFO:root:copying pyfftw/_version.py -> build/lib.linux-x86_64-cpython-312/pyfftw INFO:root:copying pyfftw/config.py -> build/lib.linux-x86_64-cpython-312/pyfftw INFO:root:copying pyfftw/__init__.py -> build/lib.linux-x86_64-cpython-312/pyfftw INFO:root:creating build/lib.linux-x86_64-cpython-312/pyfftw/builders INFO:root:copying pyfftw/builders/_utils.py -> build/lib.linux-x86_64-cpython-312/pyfftw/builders INFO:root:copying pyfftw/builders/builders.py -> build/lib.linux-x86_64-cpython-312/pyfftw/builders INFO:root:copying pyfftw/builders/__init__.py -> build/lib.linux-x86_64-cpython-312/pyfftw/builders INFO:root:creating build/lib.linux-x86_64-cpython-312/pyfftw/interfaces INFO:root:copying pyfftw/interfaces/_utils.py -> build/lib.linux-x86_64-cpython-312/pyfftw/interfaces INFO:root:copying pyfftw/interfaces/cache.py -> build/lib.linux-x86_64-cpython-312/pyfftw/interfaces INFO:root:copying pyfftw/interfaces/dask_fft.py -> build/lib.linux-x86_64-cpython-312/pyfftw/interfaces INFO:root:copying pyfftw/interfaces/numpy_fft.py -> build/lib.linux-x86_64-cpython-312/pyfftw/interfaces INFO:root:copying pyfftw/interfaces/scipy_fftpack.py -> build/lib.linux-x86_64-cpython-312/pyfftw/interfaces INFO:root:copying pyfftw/interfaces/__init__.py -> build/lib.linux-x86_64-cpython-312/pyfftw/interfaces INFO:root:copying pyfftw/interfaces/scipy_fft.py -> build/lib.linux-x86_64-cpython-312/pyfftw/interfaces INFO:root:running build_ext INFO:root:x86_64-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 -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/<>/include -I/<>/pyfftw -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include -I/usr/include -I/usr/include/python3.12 -c /tmp/pyfftw-em5b20w6/None.c -o /tmp/pyfftw-em5b20w6/None.o INFO:root:x86_64-linux-gnu-gcc /tmp/pyfftw-em5b20w6/None.o -L/usr/lib -L/usr/lib/x86_64-linux-gnu -lm -o /tmp/pyfftw-em5b20w6/a.out INFO:root:x86_64-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 -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/<>/include -I/<>/pyfftw -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include -I/usr/include -I/usr/include/python3.12 -c /tmp/pyfftw-l6u29tyw/fftw_plan_dft.c -o /tmp/pyfftw-l6u29tyw/fftw_plan_dft.o /tmp/pyfftw-l6u29tyw/fftw_plan_dft.c: In function ‘main’: /tmp/pyfftw-l6u29tyw/fftw_plan_dft.c:2:17: error: implicit declaration of function ‘fftw_plan_dft’ [-Werror=implicit-function-declaration] 2 | fftw_plan_dft(); | ^ cc1: some warnings being treated as errors WARNING:__main__:Compilation error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 INFO:root:x86_64-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 -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/<>/include -I/<>/pyfftw -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include -I/usr/include -I/usr/include/python3.12 -c /tmp/pyfftw-r_m1h4sa/fftwf_plan_dft.c -o /tmp/pyfftw-r_m1h4sa/fftwf_plan_dft.o /tmp/pyfftw-r_m1h4sa/fftwf_plan_dft.c: In function ‘main’: /tmp/pyfftw-r_m1h4sa/fftwf_plan_dft.c:2:17: error: implicit declaration of function ‘fftwf_plan_dft’ [-Werror=implicit-function-declaration] 2 | fftwf
Bug#1071722: adios4dolfinx: FTBFS: failing tests
Package: src:adios4dolfinx
Version: 0.8.1.post0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with python3 --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.12_adios4dolfinx
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
[... snipped ...]
return loop.run_sync(lambda: asyncio.ensure_future(coro))
/usr/lib/python3/dist-packages/tornado/ioloop.py:539: in run_sync
return future_cell[0].result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , engine_sets=['1716545124'])>
n = 2, activate = False
async def start_and_connect(self, n=None, activate=False):
"""Single call to start a cluster and connect a client
If `activate` is given, a blocking DirectView on all engines will be created
and activated, registering `%px` magics for use in IPython
Example::
rc = await Cluster(engines="mpi").start_and_connect(n=8, activate=True)
%px print("hello, world!")
Equivalent to::
await self.start_cluster(n)
client = await self.connect_client()
await client.wait_for_engines(n, block=False)
.. versionadded:: 7.1
.. versionadded:: 8.1
activate argument.
"""
if n is None:
n = self.n
await self.start_cluster(n=n)
client = await self.connect_client()
if n is None:
# number of engines to wait for
# if not specified, derive current value from EngineSets
n = sum(engine_set.n for engine_set in self.engines.values())
if n:
await asyncio.wrap_future(
client.wait_for_engines(n, block=False,
timeout=self.engine_timeout)
)
E ipyparallel.error.EngineError: Engine set stopped: {'exit_code': 1,
'pid': 68323, 'identifier': 'ipengine-1716545123-wyql-1716545124-64152'}
/usr/lib/python3/dist-packages/ipyparallel/cluster/cluster.py:759: EngineError
___ ERROR at setup of test_read_write_3D_vector_non_simplex[4-NCF-True-True] ___
@pytest.fixture(scope="module")
def cluster():
cluster = ipp.Cluster(engine_launcher_class="mpi", n=2)
rc = cluster.start_and_connect_sync()
tests/conftest.py:15:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/ipyparallel/_async.py:73: in _synchronize
return _asyncio_run(async_f(*args, **kwargs))
/usr/lib/python3/dist-packages/ipyparallel/_async.py:19: in _asyncio_run
return loop.run_sync(lambda: asyncio.ensure_future(coro))
/usr/lib/python3/dist-packages/tornado/ioloop.py:539: in run_sync
return future_cell[0].result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , engine_sets=['1716545124'])>
n = 2, activate = False
async def start_and_connect(self, n=None, activate=False):
"""Single call to start a cluster and connect a client
If `activate` is given, a blocking DirectView on all engines will be created
and activated, registering `%px` magics for use in IPython
Example::
rc = await Cluster(engines="mpi").start_and_connect(n=8, activate=True)
%px print("hello, world!")
Equivalent to::
await self.start_cluster(n)
client = await self.connect_client()
await client.wait_for_engines(n, block=False)
.. versionadded:: 7.1
.. versionadded:: 8.1
activate argument.
"""
if n is None:
n = self.n
await self.start_cluster(n=n)
client = await self.connect_client()
if n is None:
# number of engines to wait for
# if not specified, derive current value from EngineSets
n = sum(engine_set.n for engine_set in self.engines.values())
if n:
await asyncio.wrap_future(
client.wait_for_engines(n, block=False,
timeout=self.engine_timeout)
)
E ipyparallel.error.EngineError: Engine set stopped: {'exit_code': 1,
'pid': 68323, 'identifier': 'ipengine-1716545123-wyql-1716545124-64152'}
/usr/lib/python3/dist-packages/ipyparallel/cluster/cluster.py:759: EngineError
__ ERROR at setup of test_
Bug#1071317: intel-mkl: FTBFS: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory)
Package: src:intel-mkl Version: 2020.4.304-4 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' ../intel-mkl_2020.4.304.orig.tar.gz: OK rpm --rebuilddb error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory) make[1]: *** [debian/rules:35: extract-rpms] Error 255 make[1]: Leaving directory '/<>' make: *** [debian/rules:27: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202405/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1070919: compyle: FTBFS in bullseye
El 14/5/24 a las 7:15, Antonio Valentino escribió: On Sat, 11 May 2024 21:46:59 +0200 Santiago Vila wrote: E error: unknown target CPU 'generic' I'm sorry but I have no clue about this issue. Looking at the log It seems that the CPU is not recognized. Yes, that's what it seems. Not sure, however if the issue is in compyle or in pyopencl. Do you have an idea if the updated versions of the package (e.g. the ones currently in stable or in unstable) build properly on the same platform? I tried building compyle_0.8.1-4 (bookworm version) in a bullseye chroot, and it failed with a similar error. On the other hand, both packages (compyle and pyopencl) build fine in bookworm (that's why the bugs are marked as closed in the bookworm version) in the same platform. So yes, this seems to be a problem in pyopencl. Because this is oldstable and packages are not expected to change, I think that whoever wants to build this from source will be able to use nocheck. Therefore, I think it would be ok to forget about this one. If you are curious, I'm filing these bugs because the last point release of bullseye will be the last one, so this is the last opportunity to have a distribution which builds from source. Release Policy does not apply anymore, so it is up to the individual maintainers to decide if they want to fix the bugs or not. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1070950: Processed: pysph: FTBFS in bullseye
owner 1070950 sanv...@debian.org thanks El 12/5/24 a las 8:36, Santiago Vila escribió: Another option is that I simply change NPROCS to 1 as you point out, verify that it works, including machines with a single cpu, and do the proposed-updates upload (but in this case the mystery of mpi would remain being a mystery). Well, I think I'm going to do that (if it's ok for you). Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1070950: Processed: pysph: FTBFS in bullseye
[ adding 1070...@bugs.debian.org to the loop ] El 12/5/24 a las 7:42, Antonio Valentino escribió: Dear Santiago, Il 11/05/24 21:55, Debian Bug Tracking System ha scritto: Processing control commands: close -1 1.0~b1-5 Bug #1070950 [src:pysph] pysph: FTBFS in bullseye Marked as fixed in versions pysph/1.0~b1-5. Bug #1070950 [src:pysph] pysph: FTBFS in bullseye Marked Bug as done From a very quick look to the log excerpt IMHO it could be enough to set `NPROCS=1` in d/rules. But I understand that you have already solved the issue, right? Thanks a lot for your interest. Here is the "long explanation": The issue happens in bullseye but not in bookworm, that's why I marked it as closed in the bookmorm version. I've done it that way because Release Managers usually ask that we are strict with version tracking. This is counter-intuitive for me, but I don't want it to be a reason for dispute. This error is a little bit strange. I used a machine of type m6a.large (which has 2 vCPUs) in both bullseye and bookworm, and the line NPROCS=2 is present in both bullseye and bookworm. But it fails in bullseye and it builds ok in bookworm. I suspect it must be an MPI artifact of some sort, but I don't know enough about MPI to tell. If somebody helps me to debug it, I'll gladly take care of everything else, since I joined Debian Science precisely to deal with the bureaucracy of fixing ftbfs bugs in oldstable and stable. (If you volunteer, contact me privately and I can create a VM for you) Another option is that I simply change NPROCS to 1 as you point out, verify that it works, including machines with a single cpu, and do the proposed-updates upload (but in this case the mystery of mpi would remain being a mystery). Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1070952: ros-vcstools: FTBFS in bullseye
Package: src:ros-vcstools Version: 0.1.42-3 Severity: serious Control: close -1 0.1.42-7 Tags: ftbfs bullseye Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:232: python3.9 setup.py config /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:232: /usr/bin/python3 setup.py build /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp [... snipped ...] 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_into_subdir_without_existing_parent (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_specific_version_and_update (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_current_version_label (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 5 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 5 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_environment_metadata (test.test_hg.HGClientTest) ... ok test_get_remote_version (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved abort: destination '/tmp/tmp18ac112f/local' is not empty pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_type_name (test.test_hg.HGClientTest) ... ok test_get_url_by_reading (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_url_nonexistant (test.test_hg.HGClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved testStatusUntracked (test.test_hg.HGDiffStatClientTest) ... ok test_diff (test.test_hg.HGDiffStatClientTest) ... ok test_diff_relpath (test.test_hg.HGDiffStatClientTest) ... ok test_get_version_modified (test.test_hg.HGDiffStatClientTest) ... ok test_hg_diff_path_change_None (test.test_hg.HGDiffStatClientTest) ... ok test_status (test.test_hg.HGDiffStatClientTest) ... ok test_status_relpath (test.test_hg.HGDiffStatClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_export_repository (test.test_hg.HGExportRepositoryClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_get_branches (test.test_hg.HGGetBranchesClientTest) ... pulling from /tmp/tmpuikleq_q/remote searching for changes no changes found fixed.txt already tracked! pulling from /tmp/tmpuikleq_q/remote searching for changes adding changesets adding manifests adding file changes added 1 changesets with 0 changes to 0 files new changesets 422f3e5d8335 (run 'hg update' to get a w
Bug#1070950: pysph: FTBFS in bullseye
Package: src:pysph
Version: 1.0~b0~20191115.gite3d5e10-4
Severity: serious
Control: close -1 1.0~b1-5
Tags: ftbfs bullseye
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:232: python3.9 setup.py config
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File: /tmp/tmp_p5oyha8/check_omp.pyx
tree = Parsing.p_module(s, pxd, full_module_name)
/tmp/tmp_p5oyha8/check_omp.c: In function ‘__Pyx_InitGlobals’:
/tmp/tmp_p5oyha8/check_omp.c:1230:1: warning: ‘PyEval_InitThreads’ is
deprecated [-Wdeprecated-declarations]
1230 | PyEval_InitThreads();
| ^~
In file included from /usr/include/python3.9/Python.h:145,
[... snipped ...]
test simple_reduction.py failed with returncode 1
_ DumpLoadTestCase.test_dump_and_load_work_in_parallel _
self =
@mark.parallel
def test_dump_and_load_work_in_parallel(self):
run_parallel_script.run(
filename='check_dump_load.py', nprocs=nprocs, path=path
)
pysph/parallel/tests/test_parallel.py:114:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
filename = 'check_dump_load.py', args = [], nprocs = 2, timeout = 30.0
path = '/<>/.pybuild/cpython3_3.9/build/pysph/parallel/tests'
def run(filename, args=None, nprocs=2, timeout=30.0, path=None):
"""Run a python script with MPI or in serial (if nprocs=1). Kill
process
if it takes longer than the specified timeout.
Parameters:
---
filename - filename of python script to run under mpi.
args - List of arguments to pass to script.
nprocs - number of processes to run (1 => serial non-mpi run).
timeout - time in seconds to wait for the script to finish running,
else raise a RuntimeError exception.
path - the path under which the script is located
Defaults to the location of this file (__file__), not curdir.
"""
if args is None:
args = []
file_path = abspath(join(path, filename))
cmd = [sys.executable, file_path] + args
if nprocs > 1:
cmd = ['mpiexec', '-n', str(nprocs)] + cmd
print('running test:', cmd)
process = Popen(cmd, stdout=PIPE, stderr=PIPE)
timer = Timer(timeout, kill_process, [process])
timer.start()
out, err = process.communicate()
timer.cancel()
retcode = process.returncode
if retcode:
msg = 'test ' + filename + ' failed with returncode ' + str(retcode)
print(out.decode('utf-8'))
print(err.decode('utf-8'))
print('#'*80)
print(msg)
print('#'*80)
raise RuntimeError(msg)
E RuntimeError: test check_dump_load.py failed with returncode 1
pysph/tools/run_parallel_script.py:54: RuntimeError
- Captured stdout call -
running test: ['mpiexec', '-n', '2', '/usr/bin/python3.9',
'/<>/.pybuild/cpython3_3.9/build/pysph/parallel/tests/check_dump_load.py']
--
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:
/usr/bin/python3.9
Either request fewer slots for your application, or make more slots
available for use.
A "slot" is the Open MPI term for an allocatable unit where we can
launch a process. The number of slots available are defined by the
environment in which Open MPI processes are run:
1. Hostfile, via "slots=N" clauses (N defaults to number of
processor cores if not provided)
2. The --host command line parameter, via a ":N" suffix on the
hostname (N defaults to 1 if not provided)
3. Resource manager (e.g., SLURM, PBS/Torque, LSF, etc.)
4. If none of a hostfile, the --host command line parameter, or an
RM is present, Open MPI defaults to the number of processor cores
In all the above cases, if you want Open MPI to default to the number
of hardware threads instead of the number of processor cores, use the
--use-hwthread-cpus option.
Alternatively, you can use the --oversubscribe option to ignore the
number of available slots when deciding the number of processes to
launch.
--
###
Bug#1070919: compyle: FTBFS in bullseye
Package: src:compyle
Version: 0.7-2
Severity: serious
Control: close -1 0.8.1-4
Tags: ftbfs bullseye
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
[...]
debian/rules binary
dh binary --with python3 --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:232: python3.9 setup.py config
running config
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:232: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.9_compyle/build/compyle
copying compyle/ast_utils.py ->
/<>/.pybuild/cpython3_3.9_compyle/build/compyle
[... snipped ...]
E pyopencl._cl.RuntimeError: clBuildProgram failed: BUILD_PROGRAM_FAILURE
- clBuildProgram failed: BUILD_PROGRAM_FAILURE - clBuildProgram failed:
BUILD_PROGRAM_FAILURE
E
E Build on :
E
E error: unknown target CPU 'generic'
E
E (options: -I /usr/lib/python3/dist-packages/pyopencl/cl)
E (source saved as /tmp/tmp_oyjksbc.cl)
/usr/lib/python3/dist-packages/pyopencl/__init__.py:579: RuntimeError
TestParallelUtilsJIT.test_scan_works_with_external_func_opencl
func =
args = (,)
kwargs = {'ary': }
key = ('gintp', .input_f
at 0x7f95841ecb80>, .output_f at 0x7f957f8b1dc0>,
'a+b', 'opencl', False, ...)
@my_decorator
def _deco(func, *args, **kwargs):
# by Michele Simionato
# http://www.phyast.pitt.edu/~micheles/python/
key = key_func(*args, **kwargs)
try:
return func._memoize_dic[key] # pylint: disable=protected-access
E KeyError: ('gintp', .input_f at 0x7f95841ecb80>,
.output_f at
0x7f957f8b1dc0>, 'a+b', 'opencl', False, True)
/usr/lib/python3/dist-packages/pytools/__init__.py:621: KeyError
During handling of the above exception, another exception occurred:
self =
def test_scan_works_with_external_func_opencl(self):
importorskip('pyopencl')
self._test_scan_with_external_func(backend='opencl')
compyle/tests/test_parallel.py:119:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
compyle/tests/test_parallel.py:712: in _test_scan_with_external_func
scan(ary=a)
compyle/parallel.py:1242: in __call__
self.scan(**kwargs)
compyle/profile.py:48: in wrapper
return method(*args, **kwargs)
compyle/jit.py:526: in __call__
c_func = self._generate_kernel(**kwargs)
:2: in _generate_kernel
???
/usr/lib/python3/dist-packages/pytools/__init__.py:628: in _deco
result = func(*args, **kwargs)
compyle/jit.py:514: in _generate_kernel
return self._generate(declarations=declarations)
compyle/parallel.py:902: in _generate
return self._generate_opencl_kernel(declarations=declarations)
compyle/parallel.py:1095: in _generate_opencl_kernel
knl = GenericScanKernel(
/usr/lib/python3/dist-packages/pyopencl/scan.py:1130: in __init__
self.finish_setup()
/usr/lib/python3/dist-packages/pyopencl/scan.py:1187: in finish_setup
self._finish_setup_impl()
/usr/lib/python3/dist-packages/pyopencl/scan.py:1284: in _finish_setup_impl
candidate_scan_info = candidate_scan_gen_info.build(
/usr/lib/python3/dist-packages/pyopencl/scan.py:887: in build
program = cl.Program(context, self.scan_src).build(options)
/usr/lib/python3/dist-packages/pyopencl/__init__.py:531: in build
self._prg, was_cached = self._build_and_catch_errors(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
build_func = . at 0x7f958409d0d0>
options_bytes = b'-I /usr/lib/python3/dist-packages/pyopencl/cl'
source = '\n#define local_barrier() barrier(CLK_LOCAL_MEM_FENCE);\n\n#define
WITHIN_KERNEL /* empty */\n#define KERNEL __kernel... {\n
psc_interval_results[psc_GID_0] = psc_partial_scan_buffer[psc_interval_end -
1];\n}\n}\n'
def _build_and_catch_errors(self, build_func, options_bytes, source=None):
try:
return build_func()
except _cl.RuntimeError as e:
msg = str(e)
if options_bytes:
msg = msg + "\n(options: %s)" % options_bytes.decode("utf-8")
if source is not None:
from tempfile import NamedTemporaryFile
srcfile = NamedTemporaryFile(mode="wt", delete=False,
suffix=".cl")
try:
srcfile.write(source)
finally:
srcfile.close()
msg = msg + "\n(source saved as %s)" % srcfile.name
code = e.code
routine = e.routine
err = _cl.RuntimeError(
_cl._ErrorRecord(
msg=msg,
code=code,
routine=routine))
# Python 3.2 outputs the whole list o
Bug#1069843: zarr: FTBFS: failing tests
Package: src:zarr Version: 2.17.2+ds-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_zarr * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/zarr copying zarr/hierarchy.py -> build/lib/zarr copying zarr/__init__.py -> build/lib/zarr copying zarr/storage.py -> build/lib/zarr copying zarr/meta_v1.py -> build/lib/zarr copying zarr/creation.py -> build/lib/zarr copying zarr/types.py -> build/lib/zarr copying zarr/util.py -> build/lib/zarr copying zarr/core.py -> build/lib/zarr copying zarr/indexing.py -> build/lib/zarr copying zarr/codecs.py -> build/lib/zarr copying zarr/convenience.py -> build/lib/zarr copying zarr/errors.py -> build/lib/zarr copying zarr/version.py -> build/lib/zarr copying zarr/attrs.py -> build/lib/zarr copying zarr/n5.py -> build/lib/zarr copying zarr/context.py -> build/lib/zarr copying zarr/sync.py -> build/lib/zarr copying zarr/meta.py -> build/lib/zarr creating build/lib/zarr/_storage copying zarr/_storage/__init__.py -> build/lib/zarr/_storage copying zarr/_storage/absstore.py -> build/lib/zarr/_storage copying zarr/_storage/v3.py -> build/lib/zarr/_storage copying zarr/_storage/store.py -> build/lib/zarr/_storage copying zarr/_storage/v3_storage_transformers.py -> build/lib/zarr/_storage creating build/lib/zarr/tests copying zarr/tests/test_sync.py -> build/lib/zarr/tests copying zarr/tests/__init__.py -> build/lib/zarr/tests copying zarr/tests/test_meta.py -> build/lib/zarr/tests copying zarr/tests/test_core.py -> build/lib/zarr/tests copying zarr/tests/test_dim_separator.py -> build/lib/zarr/tests copying zarr/tests/test_storage_v3.py -> build/lib/zarr/tests copying zarr/tests/test_convenience.py -> build/lib/zarr/tests copying zarr/tests/test_n5.py -> build/lib/zarr/tests copying zarr/tests/test_storage.py -> build/lib/zarr/tests copying zarr/tests/test_hierarchy.py -> build/lib/zarr/tests copying zarr/tests/util.py -> build/lib/zarr/tests copying zarr/tests/test_attrs.py -> build/lib/zarr/tests copying zarr/tests/test_creation.py -> build/lib/zarr/tests copying zarr/tests/conftest.py -> build/lib/zarr/tests copying zarr/tests/test_info.py -> build/lib/zarr/tests copying zarr/tests/test_filters.py -> build/lib/zarr/tests copying zarr/tests/test_util.py -> build/lib/zarr/tests copying zarr/tests/test_indexing.py -> build/lib/zarr/tests copying zarr/tests/test_meta_array.py -> build/lib/zarr/tests running egg_info creating zarr.egg-info writing zarr.egg-info/PKG-INFO writing dependency_links to zarr.egg-info/dependency_links.txt writing requirements to zarr.egg-info/requires.txt writing top-level names to zarr.egg-info/top_level.txt writing manifest file 'zarr.egg-info/SOURCES.txt' reading manifest file 'zarr.egg-info/SOURCES.txt' adding license file 'LICENSE.txt' writing manifest file 'zarr.egg-info/SOURCES.txt' installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/zarr copying build/lib/zarr/hierarchy.py -> build/bdist.linux-x86_64/wheel/zarr copying build/lib/zarr/__init__.py -> build/bdist.linux-x86_64/wheel/zarr copying build/lib/zarr/storage.py -> build/bdist.linux-x86_64/wheel/zarr creating build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_sync.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/__init__.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_meta.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_core.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_dim_separator.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_storage_v3.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_convenience.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_n5.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_storage.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_hierarchy.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/util.py -> build/bdist.linux-x86_64/wheel/zarr/tests copying build/lib/zarr/tests/test_attrs.py -> build/bdist.linu
Bug#1052902: yosys: FTBFS: make[2]: *** [Makefile:971: docs/gen_images] Error 2
El 3/12/23 a las 19:00, Daniel Gröber escribió: Hi Lucas, On Thu, Oct 26, 2023 at 09:45:53AM +0200, Lucas Nussbaum wrote: As an additional data point, I can still reproduce this. I cannot provide the buildinfo, as sbuild outputs it at the end of successful builds. Doh! Didn't think of that. Something to improve in sbuild I guess :) However, in the build log there's the list of installed packages, which might be sufficient... Since I've sucessfully rebuilt yosys agains unstable and it's still failing for you it's pretty much moot. I just thought you'd have the buildinfos at hand. I'm essentially waiting for make 4.4 to make it into Debian as Santiago pointed out it may help track this down, but if I can't repro this (and I have still never seen this) there's not much I can do without access to a system this repros on. Hi. If you are willing to try the make 4.4 route, you don't really need to wait for the official package to be uploaded for unstanle. You can just download it from ftp.gnu.org, and do the usual "./configure; make". You just have to put the "make" executable as /usr/bin/make inside your chroot (and set some environment variable). Alternatively, I can also create a machine in AWS similar to the ones used by Lucas for the mass rebuilds, please contact me privately for details. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1058623: bullseye-pu: package pyzoltan/1.0.1-2+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: pyzol...@packages.debian.org, sanv...@debian.org Control: affects -1 + src:pyzoltan [ Reason ] This upload fixes Bug #1055625. FTBFS on single-cpu systems. [ Impact ] Anybody trying to build the package on a single cpu system will get an unexpected build failure. [ Tests ] I've checked that the package builds again on such systems, and also that it still builds on multi-core systems. [ Risks ] Very low. No real code changes. Only the way the tests are ran. [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] Set NPROC=1 in debian/rules so that the tests are not executed in parallel. [ Other info ] The package is already uploaded. A similar upload with a similar fix was already approved for bookworm.diff -Nru pyzoltan-1.0.1/debian/changelog pyzoltan-1.0.1/debian/changelog --- pyzoltan-1.0.1/debian/changelog 2020-04-22 21:54:56.0 +0200 +++ pyzoltan-1.0.1/debian/changelog 2023-12-13 18:40:00.0 +0100 @@ -1,3 +1,11 @@ +pyzoltan (1.0.1-2+deb11u1) bullseye; urgency=medium + + * Team upload. + * debian/rules: Set NPROC to 1 so that the package may be +built on systems with a single core. Closes: #1055625. + + -- Santiago Vila Wed, 13 Dec 2023 18:40:00 +0100 + pyzoltan (1.0.1-2) unstable; urgency=medium * [3a7ac5f] Set Standards-Verstion to 4.5.0. No changes diff -Nru pyzoltan-1.0.1/debian/gbp.conf pyzoltan-1.0.1/debian/gbp.conf --- pyzoltan-1.0.1/debian/gbp.conf 2020-03-02 21:56:35.0 +0100 +++ pyzoltan-1.0.1/debian/gbp.conf 2023-12-13 18:40:00.0 +0100 @@ -6,7 +6,7 @@ # The default name for the Debian branch is "master". # Change it if the name is different (for instance, "debian/unstable"). -debian-branch = master +debian-branch = bullseye # git-import-orig uses the following names for the upstream tags. # Change the value if you are not using git-import-orig diff -Nru pyzoltan-1.0.1/debian/rules pyzoltan-1.0.1/debian/rules --- pyzoltan-1.0.1/debian/rules 2020-04-22 21:54:40.0 +0200 +++ pyzoltan-1.0.1/debian/rules 2023-12-13 18:40:00.0 +0100 @@ -4,7 +4,7 @@ export USE_TRILINOS=1 export ZOLTAN_INCLUDE=/usr/include/trilinos export ZOLTAN_LIBRARY=/usr/lib -export NPROCS=2 +export NPROCS=1 export PYBUILD_NAME=pyzoltan -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1058559: bullseye-pu: package vlfeat/0.9.21+dfsg0-6+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: vlf...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:vlfeat
[ Reason ]
This release fixes Bug #991066: FTBFS with new imagemagick.
The bug was bullseye-ignored to avoid the package being removed,
but this upload for bullseye was still missing.
[ Impact ]
Anybody trying to build the package from source will get a build error.
[ Tests ]
I've checked that the package builds again after the fix.
[ Risks ]
Low risk. The patch was already tested in the unstable of the time.
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
Minor change to debian/rules so that the package builds again.
[ Other info ]
I've already made the upload.diff -Nru vlfeat-0.9.21+dfsg0/debian/changelog
vlfeat-0.9.21+dfsg0/debian/changelog
--- vlfeat-0.9.21+dfsg0/debian/changelog2020-02-08 06:39:32.0
+0100
+++ vlfeat-0.9.21+dfsg0/debian/changelog2023-12-12 21:30:00.0
+0100
@@ -1,3 +1,10 @@
+vlfeat (0.9.21+dfsg0-6+deb11u1) bullseye; urgency=medium
+
+ * Team upload.
+ * Apply patch by Dennis Filder to fix build error. Closes: #991066.
+
+ -- Santiago Vila Tue, 12 Dec 2023 21:30:00 +0100
+
vlfeat (0.9.21+dfsg0-6) unstable; urgency=medium
* Team upload.
diff -Nru vlfeat-0.9.21+dfsg0/debian/rules vlfeat-0.9.21+dfsg0/debian/rules
--- vlfeat-0.9.21+dfsg0/debian/rules2020-02-08 06:39:32.0 +0100
+++ vlfeat-0.9.21+dfsg0/debian/rules2023-12-12 21:26:17.0 +0100
@@ -10,12 +10,16 @@
# grab the API version from the library SONAME
API_VERSION = $(shell objdump -p bin/*/libvl.so | perl -ne
'if(/^\s+SONAME\s+libvl.so./p) {print $${^POSTMATCH}; exit;}')
+IMAGEMAGICK_POLICY := /etc/$(shell convert -version|sed -n '/^Version:
/s@Version: ImageMagick \([[:digit:]]\+\)\..*@ImageMagick-\1@p')/policy.xml
+
%:
dh $@
override_dh_auto_build:
- make PYTHON=python3 MKOCTFILE=`which mkoctfile` VERB=1 CFLAGS+=-g all
doc
-
+ mkdir -p debian/tmp/ImageMagick
+ sed -e '//s@"none"@"read|write"@' "$(IMAGEMAGICK_POLICY)" >
debian/tmp/ImageMagick/policy.xml
+ make XDG_CONFIG_HOME="$(shell pwd)/debian/tmp" PYTHON=python3
MKOCTFILE=`which mkoctfile` VERB=1 CFLAGS+=-g all doc
+ rm -Rf debian/tmp/ImageMagick
override_dh_auto_install: $(addprefix install/,data $(wildcard toolbox/*))
cp bin/*/libvl.so libvl.so.$(VERSION)
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1055625: pyzoltan: FTBFS (not enough slots available)
# Also happens in bullseye found 1055625 1.0.1-2 tags 1055625 + bullseye owner 1055625 ! thanks This happens even when using r6a.large instances from AWS, which have 2 vCPUs. I'll try to fix this for bullseye. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1057941: ycm-cmake-modules: FTBFS: TypeError: not all arguments converted during string formatting
Package: src:ycm-cmake-modules Version: 0.13.0-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --without build-stamp --with linktree dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- \ -DSPHINX_HTML=ON \ -DSPHINX_MAN=ON \ -DCMAKE_INSTALL_DOCDIR=share/doc/ycm-cmake-modules \ -DCMAKE_INSTALL_LIBDIR=share \ -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb 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/x86_64-linux-gnu -DSPHINX_HTML=ON -DSPHINX_MAN=ON -DCMAKE_INSTALL_DOCDIR=share/doc/ycm-cmake-modules -DCMAKE_INSTALL_LIBDIR=share -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF .. -- YCM Version: 0.13.0 (0.13.0) CMake Warning (dev) at find-modules/CMakeLists.txt:51 (message): A "FindGSL.cmake" module already exists in CMAKE_ROOT. Please remove it, or move it to proposed. This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at find-modules/CMakeLists.txt:51 (message): A "FindOpenGL.cmake" module already exists in CMAKE_ROOT. Please remove it, or move it to proposed. This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at deprecated/CMakeLists.txt:19 (message): A "FindGLUT.cmake" module already exists in CMAKE_ROOT. Please remove it, or move it to proposed. This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring done (0.5s) -- Generating done (0.0s) CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY CMAKE_FIND_USE_PACKAGE_REGISTRY FETCHCONTENT_FULLY_DISCONNECTED -- Build files have been written to: /<>/obj-x86_64-linux-gnu make[1]: Leaving directory '/<>' dh_prep debian/rules override_dh_auto_install make[1]: Entering directory '/<>' dh_auto_install cd obj-x86_64-linux-gnu && make -j2 install DESTDIR=/<>/debian/ycm-cmake-modules AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f modules/CMakeFiles/modules.dir/build.make modules/CMakeFiles/modules.dir/depend make -f find-modules/CMakeFiles/find-modules.dir/build.make find-modules/CMakeFiles/find-modules.dir/depend make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/modules /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/modules /<>/obj-x86_64-linux-gnu/modules/CMakeFiles/modules.dir/DependInfo.cmake "--color=" make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/find-modules /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/find-modules /<>/obj-x86_64-linux-gnu/find-modules/CMakeFiles/find-modules.dir/DependInfo.cmake "--color=" make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f find-modules/CMakeFiles/find-modules.dir/build.make find-modules/CMakeFiles/find-modules.dir/build make -f modules/CMakeFiles/modules.dir/build.make modules/CMakeFiles/modules.dir/build make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E echo_append make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E echo_append cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E touch /<>/obj-x86_64-linux-gnu/modules/CMakeFiles/modules.dir/ycm_download-complete cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E touch /<>/obj-x86_64-linux-gnu/find-modules/CMakeFiles/find-modules.dir/ycm_download-complete cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E echo_append cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E echo_append cd /<>/obj-x86
Bug#1057593: python-escript: FTBFS: RuntimeError: Unknown key (ASFLAGS_FOR_BUILD) in dpkg-buildflags
Package: src:python-escript
Version: 5.6-5
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build -v
dh_update_autotools_config -O-v
dh_autoreconf -O-v
dh_auto_configure -O-v
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Build steps for py3
mkdir -p /<>/debian/stage3
scons -j2 cc_optim=' -O3 ' build_dir=/<>/debian/tmp3 verbose=on
prefix=/<>/debian/stage3 options_file=debian/sid_options.py docs
scons: Reading SConscript files ...
3.11.6 (main, Oct 8 2023, 05:06:43) [GCC 13.2.0]
RuntimeError: Unknown key (ASFLAGS_FOR_BUILD) in dpkg-buildflags:
File "/<>/SConstruct", line 172:
env = Environment(tools = ['default'], options = vars,
File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 1231:
variables.Update(self)
File "/usr/lib/python3/dist-packages/SCons/Variables/__init__.py", line 187:
exec(contents, {}, values)
File "", line 84:
File "/<>/site_scons/extractdebbuild.py", line 52:
raise RuntimeError("Unknown key ("+key+") in dpkg-buildflags")
make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:38: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202312/
About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1057574: lmfit-py: FTBFS: mportError: The `scipy` install you are using seems to be broken, (extension modules cannot be imported), please try reinstalling.
Package: src:lmfit-py
Version: 1.2.2-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
pybuild --configure -i python{version} -p "3.12 3.11"
dh_auto_build -O--buildsystem=pybuild
pybuild --build -i python{version} -p "3.12 3.11"
I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build"
module
I: pybuild base:310: python3.12 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.12_lmfit
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/lmfit
copying lmfit/__init__.py -> build/lib/lmfit
copying lmfit/confidence.py -> build/lib/lmfit
copying lmfit/version.py -> build/lib/lmfit
copying lmfit/models.py -> build/lib/lmfit
copying lmfit/printfuncs.py -> build/lib/lmfit
copying lmfit/_ampgo.py -> build/lib/lmfit
copying lmfit/parameter.py -> build/lib/lmfit
copying lmfit/minimizer.py -> build/lib/lmfit
copying lmfit/jsonutils.py -> build/lib/lmfit
copying lmfit/conf_emcee.py -> build/lib/lmfit
copying lmfit/model.py -> build/lib/lmfit
copying lmfit/lineshapes.py -> build/lib/lmfit
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/__init__.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/confidence.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/version.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/models.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/printfuncs.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/_ampgo.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/parameter.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/minimizer.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/jsonutils.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/conf_emcee.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/model.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/lineshapes.py -> build/bdist.linux-x86_64/wheel/lmfit
running install_egg_info
running egg_info
writing lmfit.egg-info/PKG-INFO
writing dependency_links to lmfit.egg-info/dependency_links.txt
writing requirements to lmfit.egg-info/requires.txt
writing top-level names to lmfit.egg-info/top_level.txt
reading manifest file 'lmfit.egg-info/SOURCES.txt'
adding license file 'LICENSE'
adding license file 'AUTHORS.txt'
writing manifest file 'lmfit.egg-info/SOURCES.txt'
Copying lmfit.egg-info to build/bdist.linux-x86_64/wheel/lmfit-1.2.2.egg-info
running install_scripts
creating build/bdist.linux-x86_64/wheel/lmfit-1.2.2.dist-info/WHEEL
creating
'/<>/.pybuild/cpython3_3.12_lmfit/.tmp-8rugln1l/lmfit-1.2.2-py3-none-any.whl'
and adding 'build/bdist.linux-x86_64/wheel' to it
adding 'lmfit/__init__.py'
adding 'lmfit/_ampgo.py'
adding 'lmfit/conf_emcee.py'
adding 'lmfit/confidence.py'
adding 'lmfit/jsonutils.py'
adding 'lmfit/lineshapes.py'
adding 'lmfit/minimizer.py'
adding 'lmfit/model.py'
adding 'lmfit/models.py'
adding 'lmfit/parameter.py'
adding 'lmfit/printfuncs.py'
adding 'lmfit/version.py'
adding 'lmfit-1.2.2.dist-info/AUTHORS.txt'
adding 'lmfit-1.2.2.dist-info/LICENSE'
adding 'lmfit-1.2.2.dist-info/METADATA'
adding 'lmfit-1.2.2.dist-info/WHEEL'
adding 'lmfit-1.2.2.dist-info/top_level.txt'
adding 'lmfit-1.2.2.dist-info/RECORD'
removing build/bdist.linux-x86_64/wheel
Successfully built lmfit-1.2.2-py3-none-any.whl
I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.12 with
"installer" module
I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
module
I: pybuild base:310: python3.11 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.11_lmfit
* Building wheel...
running bdist_wheel
running build
running build_py
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/__init__.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/confidence.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/version.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/models.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/printfuncs.py -> build/bdist.linux-x86_64/wheel/lmfit
copying build/lib/lmfit/_ampgo.py -> build/bdist.linux-x86_64/wheel/lmfit
copying
Bug#1055859: bookworm-pu: package pyzoltan/1.0.1-5+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: pyzol...@packages.debian.org, sanv...@debian.org Control: affects -1 + src:pyzoltan [ Reason ] This upload fixes Bug#1055625 FTBFS on single-cpu systems. [ Impact ] Anybody trying to build the package using a single-cpu system will get an unexpected build error. [ Tests ] There are no real code changes. The package builds the same. [ Risks ] Very low risk. [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] The only change has been to change NPROCS=2 to NPROCS=1 in debian/rules. [ Other info ] The package is already uploaded.diff -Nru pyzoltan-1.0.1/debian/changelog pyzoltan-1.0.1/debian/changelog --- pyzoltan-1.0.1/debian/changelog 2022-10-31 08:07:44.0 +0100 +++ pyzoltan-1.0.1/debian/changelog 2023-11-12 23:25:00.0 +0100 @@ -1,3 +1,11 @@ +pyzoltan (1.0.1-5+deb12u1) bookworm; urgency=medium + + * Team upload. + * debian/rules: Set NPROC to 1 so that the package may be +built on systems with a single core. Closes: #1055625. + + -- Santiago Vila Sun, 12 Nov 2023 23:25:00 +0100 + pyzoltan (1.0.1-5) unstable; urgency=medium * Standards version bumped to 4.6.1 (non changes). diff -Nru pyzoltan-1.0.1/debian/rules pyzoltan-1.0.1/debian/rules --- pyzoltan-1.0.1/debian/rules 2022-10-31 08:07:44.0 +0100 +++ pyzoltan-1.0.1/debian/rules 2023-11-12 23:20:43.0 +0100 @@ -4,7 +4,7 @@ export USE_TRILINOS=1 export ZOLTAN_INCLUDE=/usr/include/trilinos export ZOLTAN_LIBRARY=/usr/lib -export NPROCS=2 +export NPROCS=1 export PYBUILD_NAME=pyzoltan -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1055625: pyzoltan: FTBFS (not enough slots available)
tags 1055625 + patch thanks Ok, thanks to the fact that the package is reproducible, I've just checked that the package builds the same regardless of NPROCS being set to 1 or 2 in debian/rules. Therefore, we can build it using NPROCS = 1 for everybody, and nothing is lost. As I said before, this is a small package and there is no real benefit by running the tests in parallel. Proposed patch follows. Thanks.--- a/debian/rules +++ b/debian/rules @@ -4,7 +4,8 @@ export DEB_BUILD_MAINT_OPTIONS=hardening=+all export USE_TRILINOS=1 export ZOLTAN_INCLUDE=/usr/include/trilinos export ZOLTAN_LIBRARY=/usr/lib -NPROCS?=2 + +NPROCS = 1 export NPROCS export PYBUILD_NAME=pyzoltan -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1055625: pyzoltan: FTBFS (not enough slots available)
Package: src:pyzoltan
Version: 1.0.1-5
Severity: important
Tags: ftbfs
Dear maintainer:
During a mass-rebuild of all packages in bookworm, this
package failed to build in this way:
[...]
raise RuntimeError(msg)
E RuntimeError: test geometric_partitioner.py failed with returncode 1
pyzoltan/tools/run_parallel_script.py:54: RuntimeError
- Captured stdout call -
running test: ['mpiexec', '-n', '2', '/usr/bin/python3.11',
'/<>/.pybuild/cpython3_3.11_pyzoltan/build/pyzoltan/core/tests/geometric_partitioner.py']
--
There are not enough slots available in the system to satisfy the 2
slots that were requested by the application:
/usr/bin/python3.11
Either request fewer slots for your application, or make more slots
available for use.
[...]
Apparently the package is assuming I have at least 2 CPUs,
but I have only one, and build-essential does not imply multi-core.
I tried to fix this by honoring parallel=n in DEB_BUILD_OPTIONS,
since that's the recommended way to support parallelism
when building Debian packages.
The result is in the attached patches, but they don't work.
When I use those patches, build with a single-cpu now works,
but build in my desktop PC, which has 6 cores (12 threads)
fails in this way:
---
pyzoltan/tools/run_parallel_script.py:56: RuntimeError
- Captured stdout call -
running test: ['mpiexec', '-n', '12', '/usr/bin/python3.11',
'/<>/.pybuild/cpython3_3.11_pyzoltan/build/pyzoltan/core/tests/geometric_partitioner.py']
--
There are not enough slots available in the system to satisfy the 12
slots that were requested by the application:
---
Considering that the package takes less than one minute to build,
my proposal to fix this (for everybody) would be to just disable
parallelism. Honoring parallel=n in DEB_BUILD_OPTIONS makes
sense for big packages (or even medium-sized). For small packages
like this one, there is not a great saving.
To reproduce the problem please try GRUB_CMDLINE_LINUX="nr_cpus=1",
that's an extremely easy way to test it in a machine with a single CPU.
[ Note: I'd like to fix this in stable, and I will gladly care
about the stable upload, but once we know how to fix this properly
in trixie/sid ].
Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,11 @@ export DEB_BUILD_MAINT_OPTIONS=hardening=+all
export USE_TRILINOS=1
export ZOLTAN_INCLUDE=/usr/include/trilinos
export ZOLTAN_LIBRARY=/usr/lib
-NPROCS?=2
+
+NPROCS = 1
+ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
+ NPROCS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
+endif
export NPROCS
export PYBUILD_NAME=pyzoltan
--- /dev/null
+++ b/debian/patches/0004-fix-nprocs.patch
@@ -0,0 +1,20 @@
+--- pyzoltan-1.0.1.orig/pyzoltan/tools/run_parallel_script.py
pyzoltan-1.0.1/pyzoltan/tools/run_parallel_script.py
+@@ -4,6 +4,8 @@ from subprocess import Popen, PIPE
+ import sys
+ from threading import Timer
+
++import os
++nprocs = int(os.environ.get('NPROCS', '1'))
+
+ def get_directory(file):
+ return dirname(abspath(file))
+@@ -14,7 +16,7 @@ def kill_process(process):
+ process.kill()
+
+
+-def run(filename, args=None, nprocs=2, timeout=30.0, path=None):
++def run(filename, args=None, nprocs=nprocs, timeout=30.0, path=None):
+ """Run a python script with MPI or in serial (if nprocs=1). Kill process
+ if it takes longer than the specified timeout.
+
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
0001-Fix-nprocs.patch
0002-Package-data.patch
0003-Spelling.patch
+0004-fix-nprocs.patch
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1055458: mpi-defaults: Please add hurd-amd64 cases
Hi. Just FYI: After the upload, the package is currently BD-Uninstallable on hurd-amd64: https://buildd.debian.org/status/package.php?p=mpi-defaults&suite=sid (I guess this should be fixed somewhere else). Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1055458: mpi-defaults: Please add hurd-amd64 cases
owner 1050845 ! owner 1055458 ! thanks El 6/11/23 a las 20:13, Samuel Thibault escribió: AIUI the debian/control part is auto-generated. Oh, I see. There is a control.in and a control (mandated by policy), and dpkg-buildpackage aborts if control is not ok. I use a similar trick in base-files indeed :-) Great, I'll try to care about both bugs. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1055458: mpi-defaults: Please add hurd-amd64 cases
El 6/11/23 a las 19:01, Samuel Thibault escribió: Source: mpi-defaults Version: 1.14 Severity: important Tags: patch Hello, Could you apply the attached patch to add hurd-amd64 support? Hello. There is a very similar request here for loong64: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050845 but your patch is a lot smaller. Are you sure that your patch is complete? Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#934036: sketch: FTBFS in stretch (LaTeX error)
Version: 1:0.3.7-11 Hi. Since stretch is no longer supported, I'm closing my own bug using buster version. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1052902: yosys: FTBFS: make[2]: *** [Makefile:971: docs/gen_images] Error 2
El 26/9/23 a las 16:50, Daniel Gröber escribió: Hi Lucas, On Tue, Sep 26, 2023 at 03:43:28PM +0200, Lucas Nussbaum wrote: Source: yosys Version: 0.33-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie The full build log is available from: http://qa-logs.debian.net/2023/09/25/yosys_0.33-5_unstable.log Is the buildinfo file for the rebuild available somewhere too? I'd like to diff the build environment against what the buildds had. Hello. A few months ago I made the experiment of building the archive with the new "make --shuffle" feature from make 4.4. See: https://trofi.github.io/posts/238-new-make-shuffle-mode.html for details. Well, "yosys" was one of the packages which FTBFS for me. It was version 0.23-6, and it failed in a different way. But something tells me that this bug reported by Lucas could easily be another Makefile bug. So, instead of trying to reproduce the problem by building the package in your machine, I suggest that you take the provided build log, collate it with the current Makefiles, and try to determine how could it happen at all. For example, the build log says this: I can't find file `verilog_flow.aux'. The interesting question here would be: Are you sure that the Makefiles are correctly written in such a way that the verilog_flow.aux file is always created before some other process tries to use it? Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1016958: epics-base: FTBFS without network access
El 28/2/23 a las 12:53, Andrius Merkys escribió: On a related note, is trying network access to localhost RC? It's ok if you try to connect to a service started by the build process itself (please downgrade again if my severity change was wrong). This is the exact wording in policy: For packages in the main archive, required targets must not attempt network access, except, via the loopback interface, to services on the build host that have been started by the build. It is not ok if you try to use a service which was already running in the host machine. Here is a funny example of that: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028163 I guess that according to the spirit of the norm, it's also not ok to do DNS queries, as that's "communication with the outside world". Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1016958: epics-base: FTBFS without network access
severity 1016958 serious thanks Hello. Merely trying network access is already considered RC, so this should really be serious. (I would be willing to test a fix if somebody proposes one). Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1031064: armci-mpi: FTBFS randomly (autobuilder hangs)
Package: src:armci-mpi
Version: 0.3.1~beta-6
Severity: important
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules build-arch
dh build-arch --with autoreconf
dh_update_autotools_config -a
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
rm -rf /<>/pristine-src /<>/build-mpich
/<>/build-openmpi
tmpdir=`mktemp -d`; \
cp -ra /<>/* ${tmpdir}; \
mv $tmpdir /<>/pristine-src
dh_autoreconf --as-needed --sourcedirectory=/<>/pristine-src
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'm4'.
libtoolize: copying file 'm4/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:99: warning: The macro `AC_CONFIG_HEADER' is obsolete.
configure.ac:99: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:99: the top level
configure.ac:110: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:110: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/aclocal_cc.m4:595: PAC_ARG_STRICT is expanded from...
configure.ac:110: the top level
configure.ac:110: warning: The macro `AC_FD_CC' is obsolete.
configure.ac:110: You should run autoupdate.
./lib/autoconf/general.m4:399: AC_FD_CC is expanded from...
m4/aclocal_cc.m4:38: PAC_C_CHECK_COMPILER_OPTION is expanded from...
m4/aclocal_cc.m4:431: PAC_CC_STRICT is expanded from...
m4/aclocal_cc.m4:595: PAC_ARG_STRICT is expanded from...
configure.ac:110: the top level
configure.ac:130: warning: The macro `AC_PROG_CC_C99' is obsolete.
configure.ac:130: You should run autoupdate.
./lib/autoconf/c.m4:1659: AC_PROG_CC_C99 is expanded from...
configure.ac:130: the top level
configure.ac:132: warning: The macro `AC_ERROR' is obsolete.
configure.ac:132: You should run autoupdate.
./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
configure.ac:132: the top level
configure.ac:140: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:140: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:140: the top level
configure.ac:156: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:156: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:156: the top level
configure.ac:178: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:178: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:178: the top level
configure.ac:188: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:188: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:188: the top level
configure.ac:198: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:198: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:198: the top level
configure.ac:208: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:208: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:208: the top level
configure.ac:213: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:213: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
m4/aclocal_cc.m4:209: PAC_PROG_C_WEAK_SYMBOLS is expanded from...
configure.ac:213: the top level
configure.ac:213: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.ac:213: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
m4/aclocal_cc.m4:209: PAC_PROG_C_WEAK_SYMBOLS is expanded from...
configure.ac:213: the top level
configure.ac:230: warning: AC_OUTPUT should be used without arguments.
configure.ac:230: You should run autoupdate.
configure.ac:31: installing 'm4/ar-lib'
configure.ac:20: installing 'm4/compile'
configure.ac:33: installing 'm4/config.guess'
configure.ac:33: installing 'm4/config.sub'
configure.ac:10: installing 'm4/install-sh'
configure.ac:10: installing 'm4/missing'
Makefile.am: installing 'm4/depcomp'
parallel-tests: installing 'm4/test-drive
Bug#1030906: taurus-pyqtgraph: FTBFS (failing tests)
Package: src:taurus-pyqtgraph Version: 0.5.9-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --with python3 --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:240: python3.11 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:240: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/datainspectortool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/autopantool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/buffersizetool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/dateaxisitem.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/taurustrendset.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/plot.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/forcedreadtool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/y2axis.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/curvesmodel.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/curveproperties.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/taurusimageitem.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/__init__.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/trend.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/curvespropertiestool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/taurusmodelchoosertool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/util.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/taurusplotdataitem.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/cli.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph copying taurus_pyqtgraph/legendtool.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph creating /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/legendExample.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/taurustrendset.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/axislabels.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/y2axis.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/__init__.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples copying taurus_pyqtgraph/examples/taurusplotdataitem.py -> /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples running egg_info creating taurus_pyqtgraph.egg-info writing taurus_pyqtgraph.egg-info/PKG-INFO writing dependency_links to taurus_pyqtgraph.egg-info/dependency_links.txt writing entry points to taurus_pyqtgraph.egg-info/entry_points.txt writing requirements to taurus_pyqtgraph.egg-info/requires.txt writing top-level names to taurus_pyqtgraph.egg-info/top_level.txt writing manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt' reading manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' warning: no files found matching '*.jpg' under directory 'docs' warning: no files found matching '*.png' under directory 'docs' warning: no files found matching '*.gif' under directory 'docs' adding license file 'LICENSE.txt' writing manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: SetuptoolsDeprecationWarning: Installing 'taurus_pyqtgraph.ui' as data is deprecated, please list it in `packages`. !! # Package would be ignored #
Bug#1030905: sardana: FTBFS (cannot import name 'getargspec' from 'sphinx.util.inspect')
Package: src:sardana
Version: 3.0.3-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py config
/<>/setup.py:27: DeprecationWarning: the imp module is deprecated
in favour of importlib and slated for removal in Python 3.12; see the module's
documentation for alternative uses
import imp
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3 setup.py build
/<>/setup.py:27: DeprecationWarning: the imp module is deprecated
in favour of importlib and slated for removal in Python 3.12; see the module's
documentation for alternative uses
import imp
running build
[... snipped ...]
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/helper.py
to helper.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/res/controllers/ROI.py
to ROI.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/test_synchronization.py
to test_synchronization.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/test_poolmotor.py
to test_poolmotor.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/test_poolpseudocounter.py
to test_poolpseudocounter.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/pool/test/util.py
to util.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/test/testsuite.py
to testsuite.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/test/test_sardanabuffer.py
to test_sardanabuffer.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/test/__init__.py
to __init__.cpython-311.pyc
byte-compiling
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana/test/test_sardanavalue.py
to test_sardanavalue.cpython-311.pyc
running install_egg_info
Copying src/sardana.egg-info to
/<>/debian/python3-sardana/usr/lib/python3.11/dist-packages/sardana-3.0.3.egg-info
Skipping SOURCES.txt
running install_scripts
Installing MacroServer script to /<>/debian/python3-sardana/usr/bin
Installing Pool script to /<>/debian/python3-sardana/usr/bin
Installing Sardana script to /<>/debian/python3-sardana/usr/bin
Installing sardanatestsuite script to
/<>/debian/python3-sardana/usr/bin
Installing spock script to /<>/debian/python3-sardana/usr/bin
Installing diffractometeralignment script to
/<>/debian/python3-sardana/usr/bin
Installing hklscan script to /<>/debian/python3-sardana/usr/bin
Installing macroexecutor script to
/<>/debian/python3-sardana/usr/bin
Installing sequencer script to /<>/debian/python3-sardana/usr/bin
Installing showscan script to /<>/debian/python3-sardana/usr/bin
Installing ubmatrix script to /<>/debian/python3-sardana/usr/bin
I: pybuild pybuild:333: dh_numpy3
dh_installdocs -i -O--buildsystem=pybuild
debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom \
PYBUILD_BUILD_ARGS="cd doc && PYTHONPATH={build_dir} http_proxy='127.0.0.1:9'
{interpreter} -m sphinx -N -bhtml source build/html" dh_auto_build # HTML generator
I: pybuild base:240: cd doc &&
PYTHONPATH=/<>/.pybuild/cpython3_3.11_sardana/build
http_proxy='127.0.0.1:9' python3.11 -m sphinx -N -bhtml source build/html
Running Sphinx v5.3.0
Extension error:
Could not import extension sardanaextension (exception: cannot import name
'getargspec' from 'sphinx.util.inspect'
(/usr/lib/python3/dist-packages/sphinx/util/inspect.py))
E: pybuild pybuild:388: build: plugin custom failed with: exit code=2: cd doc &&
PYTHONPATH=/<>/.pybuild/cpython3_3.11_sardana/build
http_proxy='127.0.0.1:9' python3.11 -m sphinx -N -bhtml source build/html
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit
code 13
make[1]: *** [debian/rules:15: override_dh_sphinxdoc] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
(The above is just how the build ends and not necessarily the most relevant
part)
About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a red
Bug#1029440: opm-common: FTBFS in bookworm (cc1plus: fatal error: [...]/builtin_pybind11.cpp: No such file or directory)
El 28/1/23 a las 11:49, Markus Blatt escribió: How should we proceed. Is there a possibility to do the builds on other machines with more RAM? I have just enabled 8GB of swap in the test machine I gave you. If you believe it's lack of RAM, please show me where the "out of memory" happens in the logs. If it really happens, it will leave some kind of trace somewhere. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1029440: opm-common: FTBFS in bookworm (cc1plus: fatal error: [...]/builtin_pybind11.cpp: No such file or directory)
El 27/1/23 a las 23:48, Graham Inggs escribió: Control: severity -1 important Hi Markus, Santiago As opm-common is no longer in bookworm, this bug is currently unreproducible. When I wrote "bookworm" I meant "bookworm and above". Should I change the title so that you don't interpret it literally? Also, I gave Markus ssh access to a machine where the bug is fully reproducible. Markus, any progress? Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1029440: opm-common: FTBFS in bookworm (cc1plus: fatal error: [...]/builtin_pybind11.cpp: No such file or directory)
Package: src:opm-common Version: 2022.10+ds-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --with python3 dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DOPM_ENABLE_PYTHON=1 -DOPM_INSTALL_PYTHON=1 -DPYTHON_EXECUTABLE=/usr/bin/python3 -DOPM_INSTALL_COMPILED_PYTHON=OFF -DOPM_ENABLE_EMBEDDED_PYTHON=1 -DBUILD_SHARED_LIBS=1 -DCMAKE_INSTALL_DOCDIR=share/doc/libopm-common -DPYTHON_INSTALL_PREFIX=lib/python3/dist-packages -DOPM_INSTALL_COMPILED_PYTHON=OFF -DUSE_RUNPATH=OFF -DWITH_NATIVE=OFF -DUSE_MPI=ON -DUSE_BASH_COMPLETIONS_DIR=ON -DOPM_BINARY_PACKAGE_VERSION=" lsb_release -r | sed "s/.*:\s*\([^\s]*\).*/\1/": 2022.10+ds-1" cd obj-x86_64-linux-gnu && 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 "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DOPM_ENABLE_PYTHON=1 -DOPM_INSTALL_PYTHON=1 -DPYTHON_EXECUTABLE=/usr/bin/python3 -DOPM_INSTALL_COMPILED_PYTHON=OFF -DOPM_ENABLE_EMBEDDED_PYTHON=1 -DBUILD_SHARED_LIBS=1 -DCMAKE_INSTALL_DOCDIR=share/doc/libopm-common -DPYTHON_INSTALL_PREFIX=lib/python3/dist-packages -DOPM_INSTALL_COMPILED_PYTHON=OFF -DUSE_RUNPATH=OFF -DWITH_NATIVE=OFF -DUSE_MPI=ON -DUSE_BASH_COMPLETIONS_DIR=ON "-DOPM_BINARY_PACKAGE_VERSION= lsb_release -r | sed s/.*:s*([^s]*).*/1/: 2022.10+ds-1" .. -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.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 Deprecation Warning at cmake/Modules/OpmInit.cmake:26 (cmake_policy): The OLD behavior for policy CMP0026 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. Call Stack (most recent call first): CMakeLists.txt:58 (OpmSetPolicies) CMake Warning at cmake/Modules/Findopm-tests.cmake:26 (message): opm-tests not found - integration tests using opm-tests will be skipped. Call Stack (most recent call first): CMakeLists.txt:62 (include) -- Performing Test HAVE_C99 -- Performing Test HAVE_C99 - Success -- Found C99: -std=c99 -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found suitable version "1.74.0", minimum required is "1.44.0") found components: system unit_test_framework -- Performing Test HAVE_CJSON -- Performing Test HAVE_CJSON - Success -- Found cjson: /usr/include/cjson -- Found Python3: /usr/bin/python3 (found version "3.10.9") found components: Interpreter Development Development.Module Development.Embed -- Performing Test HAS_FLTO -- Performing Test HAS_FLTO - Success -- Found pybind11: /usr/include (found version "2.10.2") -- Performing Test HAVE_ATTRIBUTE_ALWAYS_INLINE -- Performing Test HAVE_ATTRIBUTE_ALWAYS_INLINE - Success -- Performing Test HAS_ATTRIBUTE_UNUSED -- Performing Test HAS_ATTRIBUTE_UNUSED - Success -- Performing Test HAS_ATTRIBUTE_DEPRECATED -- Performing Test HAS_ATTRIBUTE_DEPRECATED - Success -- Performing Test HAS_ATTRIBUTE_DEPRECATED_MSG -- Performing Test HAS_ATTRIBUTE_DEPRECATED_MSG - Success -- CMake version: 3.25.1 -- Linux distribution: Debian GNU/Linux bookworm/sid -- Target architecture: x86_64 -- Found Git: /usr/bin/git (found version "2.39.0") -- Source code repository: not found! -- GNU C++ compiler version: 12.2.0 -- Linker: ld 2.39.50.20221224 Processing opm_defaults opm-common -- Precompiled headers: disabled -- Build type: None -- Found OpenMP_C: -fopenmp (found version "4.5") -- Found OpenMP_CXX: -fopenmp (found version "4.5") -- Found OpenMP: TRUE (found version "4.5") -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success -- Found Threads: TRUE -- Checking to see if CXX compiler accepts flag -pthread -- Checking to see if CXX compiler accepts flag -pthread - yes -- Could NOT find CppCheck (missing: CPPCHECK_PROGRAM) -- Disabling clang-check as CMAKE_EXPORT_COMPILE_COMMANDS is no
Bug#1027208: severity of 1027208 is important
severity 1027208 important thanks Hi. I think this is what you really meant. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#945461: plplot: FTBFS with tcl8.6 version 8.6.10 uploaded the same day
Package: src:plplot Version: 5.15.0+dfsg-5 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules binary-arch dh binary-arch -Scmake --with python3,ocaml dh_testdir -a -O-Scmake dh_update_autotools_config -a -O-Scmake dh_autoreconf -a -O-Scmake dh_ocamlinit -a -O-Scmake debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' sed "s/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/" < debian/plplotada.gpr.in > debian/plplotada.gpr xvfb-run dh_auto_configure -- -DCMAKE_RULE_MESSAGES=OFF -DCMAKE_VERBOSE_MAKEFILE=ON -DUSE_RPATH=OFF -DPLD_psttf=OFF -DNON_TRANSITIVE=ON -DENABLE_tk=ON -DENABLE_python=ON -DENABLE_ada=ON -DOCTAVE_OCT_DIR=/usr/lib/x86_64-linux-gnu/octave/site/oct/api-v53/x86_64-pc-linux-gnu -DBUILD_DOC=ON -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu -DBUILD_TEST=ON cd obj-x86_64-linux-gnu && 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_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_RULE_MESSAGES=OFF -DCMAKE_VERBOSE_MAKEFILE=ON -DUSE_RPATH=OFF -DPLD_psttf=OFF -DNON_TRANSITIVE=ON -DENABLE_tk=ON -DENABLE_python=ON -DENABLE_ada=ON -DOCTAVE_OCT_DIR=/usr/lib/x86_64-linux-gnu/octave/site/oct/api-v53/x86_64-pc-linux-gnu -DBUILD_DOC=ON -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu -DBUILD_TEST=ON .. -- The C compiler identification is GNU 9.2.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works [... snipped ...] -- Installing: /<>/debian/tmp/usr/share/man/man3/plsym.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plszax.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/pltext.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/pltimefmt.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plvasp.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plvect.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plvpas.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plvpor.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plvsta.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plw3d.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plwidth.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plwind.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plxormod.3plplot -- Installing: /<>/debian/tmp/usr/share/man/man3/plplot.3plplot -- Installing: /<>/debian/tmp/usr/share/doc/plplot/README.pkg-config make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' # Remove multiarch path and -fPIC in pkgconfig files. sed -i -e 's,-L"/usr/lib/x86_64-linux-gnu",,g;s, *, ,g' \ -e 's,-fPIC,,g' \ debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/*.pc # Add -fPIC compiler flag for building the C++ examples sed -i -E -e 's/^(CXX = .*)/\1 -fPIC/' \ debian/tmp/usr/share/plplot*/examples/c++/Makefile # Remove tests for shared libs on Python and ADA from export_plplot: # These libs were renamed during build for multiarch sed '/\/_Pltk_init.so/d;/\/_plplotc.so/d;/\/plplot_pyqt5_/d;/\/libplplotada.so/d' \ -i debian/tmp/usr/lib/*/cmake/plplot/export_plplot-none.cmake dh_numpy3 make[1]: Leaving directory '/<>' dh_install -a -O-Scmake dh_install: Cannot find (any matches for) "usr/lib/*/plplot*/drivers/*tk*" (tried in ., debian/tmp) dh_install: plplot-tcl missing files: usr/lib/*/plplot*/drivers/*tk* dh_install: Cannot find (any matches for) "usr/bin/plserver" (tried in ., debian/tmp) dh_install: plplot-tcl-bin missing files: usr/bin/plserver dh_install: Cannot find (any matches for) "usr/include/plplot/pltk.h" (tried in ., debian/tmp) dh_install: plplot-tcl-dev missing files: usr/include/plplot/pltk.h dh_install: Cannot find (any matches for) "usr/lib/python3*/dist-packages/_Pltk_init*.so" (tried in ., debian/tmp) dh_install: python3-plplot missing files: usr/lib/python3*/dist-packages/_Pltk_init*.so dh_install: missing files, aborting make: *** [debian/rules:43: binary-arch] Error 255 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -B" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/plplot.html where you can get a full build log if you need it. A diff between build logs shows that maybe this package, uploaded the same day: https://packages.qa.debian.org/t/tcl8.6.htmlhttps://packages.qa.debian.org/t/tcl8.6.html may have something to do with the breakage. Thanks. -- debian-science-maintainers mailing list debian-science-maintaine
Bug#907829: fixed in p4est 2.2-1
On Mon, Sep 09, 2019 at 09:37:20AM +0200, Graham Inggs wrote: > Hi Santiago > > Did you try rebuilding with: > > DEB_BUILD_OPTIONS=nocheck > > as suggested in #932795 [1] ? That's not the type of QA I'm doing. I'm trying to keep Debian buster free of FTBFS bugs like this one, and naturally me building a package with nocheck does not fix this bug. Please note that I'm not specifically asking anybody to do an upload for buster, I just hope that a fix for buster is allowed if there are people willing to do the job. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#907829: fixed in p4est 2.2-1
reopen 907829 found 907829 1.1-5 fixed 907829 2.2-1 thanks Hi. Could we please fix this in buster as well? (for some future point release) I'm still doing QA on buster and it's a real pain to find packages which FTBFS. Please let me know if you need/require/welcome help for this. Thanks. Hi. Could we please fix this in buster as well? (for some future point release) I'm still doing QA on buster and it's a real pain to find packages which FTBFS. Please let me know if you need/require/welcome help for this. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#938970: mpi4py: FTBFS when built with dpkg-buildpackage -A
Package: src:mpi4py
Version: 3.0.2-12
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf debian/rules -- cythonize
make[2]: Entering directory '/<>'
D: removing previously generated by Cython sources
find -iname *.c | xargs grep -l 'Generated by Cython' | xargs -r rm
python3 setup.py build_src
running build_src
cythonizing 'mpi4py.MPI.pyx' -> 'mpi4py.MPI.c'
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:367: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File: /<>/src/mpi4py/MPI.pxd
tree = Parsing.p_module(s, pxd, full_module_name)
[... snipped ...]
make[1]: Leaving directory '/<>'
dh_install -i -O--buildsystem=pybuild
dh_installdocs -i -O--buildsystem=pybuild
debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/<>'
dh_sphinxdoc -ppython-mpi4py-doc
make[1]: Leaving directory '/<>'
debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<>'
dh_installchangelogs CHANGES.rst
make[1]: Leaving directory '/<>'
dh_installman -i -O--buildsystem=pybuild
dh_installinfo -i -O--buildsystem=pybuild
dh_python2 -i -O--buildsystem=pybuild
dh_python3 -i -O--buildsystem=pybuild
E: dh_python3 dh_python3:176: no package to act on (python3-foo or one with
${python3:Depends} in Depends)
dh_installinit -i -O--buildsystem=pybuild
dh_installsystemduser -i -O--buildsystem=pybuild
dh_perl -i -O--buildsystem=pybuild
dh_link -i -O--buildsystem=pybuild
dh_strip_nondeterminism -i -O--buildsystem=pybuild
debian/rules override_dh_compress
make[1]: Entering directory '/<>'
dh_compress -X.py -X.html -X.css -X.jpg -X.txt -X.js -X.json -X.rtc -X.par
-X.bin -Xobjects.inv
make[1]: Leaving directory '/<>'
dh_fixperms -i -O--buildsystem=pybuild
dh_missing -i -O--buildsystem=pybuild
debian/rules override_dh_dwz
make[1]: Entering directory '/<>'
echo "dh_dwz is currently deactivated since it generates an error:
\".debug_line reference above end of section\""
dh_dwz is currently deactivated since it generates an error: ".debug_line
reference above end of section"
make[1]: Leaving directory '/<>'
debian/rules override_dh_strip
make[1]: Entering directory '/<>'
dh_strip -ppython-mpi4py --dbg-package=python-mpi4py-dbg
dh_strip: All requested packages have been excluded (e.g. via a Build-Profile
or due to architecture restrictions).
dh_strip -ppython3-mpi4py --dbg-package=python3-mpi4py-dbg
dh_strip: All requested packages have been excluded (e.g. via a Build-Profile
or due to architecture restrictions).
# dh_strip seemingly doesn't catch the PEP 3149-style debug names
rm debian/python3-mpi4py/usr/lib/python3*/*-packages/*/*.cpython-3?d*.so
rm: cannot remove
'debian/python3-mpi4py/usr/lib/python3*/*-packages/*/*.cpython-3?d*.so': No
such file or directory
make[1]: *** [debian/rules:135: override_dh_strip] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:46: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
See also:
https://buildd.debian.org/status/package.php?p=mpi4py
The usual recipe for this is to split override_dh_strip
into override_dh_strip-arch and override_dh_strip-indep.
Thanks.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#929720: hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require coroutines
Greetings. I can reproduce this bug, and I've put a bunch of failed build logs here: https://people.debian.org/~sanvila/build-logs/hkl/ The bug happens "randomly", but in a very particular way: always in some instances and never in the others. I believe this may be some sort of Makefile bug which is related to filesystem ordering or something similar, but I don't really know. In either case, I could easily offer ssh access to a machine where this happens to anybody interested in debugging the problem (please contact me privately for details). While we are at it: I'm still doing QA for buster, so I'd appreciate (once we find a fix) if we could fix this in buster as well (it's a FTBFS bug after all). I would be willing to help if required, either by preparing an upload for stable, filing a release.debian.org bug, or both. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#907829: p4est: FTBFS on single CPU machines
On Tue, 2 Oct 2018, Adrian Bunk wrote: > Everyone else uses the common-sense approach of using CPU-strong > machines for CPU-intensive tasks like package building, if you > have made different practical experiences I'd be interested in > seeing the bills. https://people.debian.org/~sanvila/single-cpu/ TLDR: For packages which require 1 GB of RAM or less to build (approximately 96% of all packages), building them on machines with 2 CPUs is 50% more expensive on average than doing so on machines with only 1 CPU. Note that the maintainers of this package quickly found a fix for the bug, and the only reason the package is still unfixed in buster is that you downgraded the bug. Had Debian Policy and the original severity been respected, the package most probably would be fixed in buster now, as there are always people applying existing patches to fix RC bugs in bug-squashing parties. So, you have not helped anything at all to raise the quality of Debian by downgrading this bug. In fact, you have helped negative. To me, this is not anymore about Debian Policy, Release Policy, or the RC-ness of a given bug, this is about trying to skip all the decision-making procedures in Debian. I'm really sorry but I have no other option than complaining to the TC in the hope that I don't have to repeat this discussion with anybody else in the future. Please subscribe to the bug I've just filed if you like: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932795 Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#926215: reassign 928405 to src:glibc, notfixed 926215 in 2.6~20180302-1, tagging 926215
On Fri, May 10, 2019 at 03:37:51PM +0200, Andreas Beckmann wrote: > The bug is now again in the bts-is-confused state: found+fixed in the > same version (which is treated as not-fixed and wont-be-archived). My > intention was to close it as invalid (found with version, fixed without > version) + unreproducible, since it is unclear which package actually > fixed it (such that a reassign+affects could be used). I don't think "found with version, fixed without version" is a good idea. Anyway, I finally managed to close the bug. If you agree we can keep it that way and let it to be archived. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#926215: dune-pdelab: FTBFS with gcc 8.3
Version: 2.6~20180302-1 On Sun, May 05, 2019 at 09:41:21AM +0100, Rebecca N. Palmer wrote: > Control: tags -1 moreinfo > > It works for me, in both sid and buster cowbuilder chroots. Same here, just tried in both buster and sid, using sbuild. So, I'm closing the bug. [ Ansgar: If you still can reproduce the assertion failure, please file a new bug. It's better not to mix different issues in the same report ]. > Has it been > fixed (the version of dune-pdelab hasn't changed, but the bug may have been > elsewhere), or is it hardware/setup dependent? I can only speak for the bug I initially reported here, which definitely seemed like a C++ problem to me and not related to the building environment. I agree with Ansgar that it was probably a problem with GCC. (It would have been nice to know where the real problem was, but probably it does not worth the effort now. If anybody is really interested, it would still be possible to do so by recreating the state of buster in the past using snapshot.debian.org). Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#926935: arpack: FTBFS (does not honor parallel=n in DEB_BUILD_OPTIONS)
On Wed, Apr 24, 2019 at 04:47:16PM +0200, Sylvestre Ledru wrote: > Le 24/04/2019 à 16:45, Santiago Vila a écrit : > > On Wed, Apr 24, 2019 at 04:24:59PM +0200, ghisv...@gmail.com wrote: > > > Anyone objecting on applying Santiago's patch to src:arpack to fix the > > > occasionnal FTBFS on single-core builders? > > > > > > If not, then I am happy to prepare a release. > > > > Thanks a lot. > > > > One minor clarification: The failure happens always on single-cpu systems, > > not just occassionally. > > > Don't hesitate to forward that upstream if you find a fix > https://github.com/opencollab/arpack-ng A general fix (i.e. one that upstream accept) would probably involve using "nproc" command inside the Makefiles, but then we would have to override that anyway to avoid using so many simultaneous jobs if the user explicitly ask for less jobs via DEB_BUILD_OPTIONS. The safe/conservative thing to do would be to use 1 job for the test suite. I can put an issue in github if you confirm there is not one yet. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#926935: arpack: FTBFS (does not honor parallel=n in DEB_BUILD_OPTIONS)
On Wed, Apr 24, 2019 at 04:24:59PM +0200, ghisv...@gmail.com wrote: > Anyone objecting on applying Santiago's patch to src:arpack to fix the > occasionnal FTBFS on single-core builders? > > If not, then I am happy to prepare a release. Thanks a lot. One minor clarification: The failure happens always on single-cpu systems, not just occassionally. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#927808: gmsh: FTBFS in buster (c++: error: unrecognized command line option '-Wint-to-void-pointer-cast')
Package: src:gmsh Version: 4.1.3+ds1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=cmake --builddirectory=/<>/gmsh-4.1.3+ds1/debian/build --with python3 dh_update_autotools_config -i -O--buildsystem=cmake -O--builddirectory=/<>/gmsh-4.1.3\+ds1/debian/build dh_autoreconf -i -O--buildsystem=cmake -O--builddirectory=/<>/gmsh-4.1.3\+ds1/debian/build debian/rules override_dh_auto_configure make[1]: Entering directory '/<>/gmsh-4.1.3+ds1' dh_auto_configure -- -DENABLE_OS_SPECIFIC_INSTALL:BOOL=ON -DENABLE_SYSTEM_CONTRIB:BOOL=ON -DENABLE_METIS:BOOL=OFF -DENABLE_MED:BOOL=OFF -DENABLE_TAUCS:BOOL=OFF -DENABLE_OSMESA:BOOL=OFF -DENABLE_CGNS:BOOL=ON -DENABLE_OCC:BOOL=ON -DENABLE_OCC_CAF:BOOL=ON -DENABLE_WRAP_PYTHON:BOOL=ON -DENABLE_BUILD_SHARED:BOOL=ON -DENABLE_BUILD_DYNAMIC:BOOL=ON -DENABLE_ONELAB:BOOL=ON -DCMAKE_SKIP_RPATH:BOOL=ON -DCMAKE_INCLUDE_PATH:STRING="/usr/include/mpi" -DOCC_INC:STRING="/usr/include/occt" -DOCC_LIB:STRING="/usr/lib/x86_64-linux-gnu" â -DCMAKE_CXX_FLAGS="-DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX -lmpi -fPIC -Wall -g -O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=. -fstack-protector-strong -Wformat -Werror=format-security" -DENABLE_MPI:BOOL=ON cd debian/build && 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_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DENABLE_OS_SPECIFIC_INSTALL:BOOL=ON -DENABLE_SYSTEM_CONTRIB:BOOL=ON -DENABLE_METIS:BOOL=OFF -DENABLE_MED:BOOL=OFF -DENABLE_TAUCS:BOOL=OFF -DENABLE_OSMESA:BOOL=OFF -DENABLE_CGNS:BOOL=ON -DENABLE_OCC:BOOL=ON -DENABLE_OCC_CAF:BOOL=ON -DENABLE_WRAP_PYTHON:BOOL=ON -DENABLE_BUILD_SHARED:BOOL=ON -DENABLE_BUILD_DYNAMIC:BOOL=ON -DENABLE_ONELAB:BOOL=ON -DCMAKE_SKIP_RPATH:BOOL=ON -DCMAKE_INCLUDE_PATH:STRING=/usr/include/mpi -DOCC_INC:STRING=/usr/include/occt -DOCC_LIB:STRING=/usr/lib/x86_64-linux-gnu â "-DCMAKE_CXX_FLAGS=-DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX -lmpi -fPIC -Wall -g -O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=. -fstack-protector-strong -Wformat -Werror=format-security" -DENABLE_MPI:BOOL=ON ../.. -- The CXX compiler identification is GNU 8.3.0 -- The C compiler identification is GNU 8.3.0 -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done [... snipped ...] make[3]: Leaving directory '/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp' make[2]: Leaving directory '/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp' Determining if the include file dlfcn.h exists passed with the following output: Change Dir: /<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_c1405/fast" make[2]: Entering directory '/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_c1405.dir/build.make CMakeFiles/cmTC_c1405.dir/build make[3]: Entering directory '/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_c1405.dir/CheckIncludeFile.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99-o CMakeFiles/cmTC_c1405.dir/CheckIncludeFile.c.o -c /<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp/CheckIncludeFile.c Linking C executable cmTC_c1405 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_c1405.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -rdynamic CMakeFiles/cmTC_c1405.dir/CheckIncludeFile.c.o -o cmTC_c1405 make[3]: Leaving directory '/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp' make[2]: Leaving directory '/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp' Determining if the include file linux/joystick.h exists passed with the following output: Change Dir: /<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_9c800/fast" make[2]: Entering directory '/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_9c800.dir/build.make CMakeFiles/cmTC_9c800.dir/build make[3]: Entering directory '/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_9c800.dir/CheckIncludeFile.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=. -fstack-protector-s
Bug#926935: tagging 926935
I said: [ lots of things ] Ok, sorry, I didn't want to sound confrontational. Just FYI: The reason this issue makes me to be upset is the discussion that took place here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907829 [ Since you applied buster-ignore here, you might want to apply buster-ignore to such bug as well instead of downgrading as Adrian did. In fact, maybe it would be good news to have it serious and buster-ignore ]. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#926935: tagging 926935
Hi. I forgot: The fact that you decided to use buster-ignore here means that it's still ok to use "serious" for these kind of bugs? Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#926935: tagging 926935
On Sat, 13 Apr 2019, Ivo De Decker wrote: > # buildds have at least 2 CPU cores However, this is still a FTBFS bug in a release architecture (amd64). We are a free software distribution. We don't agree that the end user *must* be able to rebuild the package? For the record: I can build 99.99% of Debian with a single CPU, and only a handful of packages FTBFS with a single CPU. Not 10 and not 100, only a handful. Since VPS providers have small machines where building packages is still cheaper, there is no clear benefit in "deprecating" building in single-CPU machines. So: Could I know please when exactly this started not to be RC, if that's the case? Please state exact date and how many bugs had to be downgraded after the decision was made (AFAIK, this has never happened). Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#926935: arpack: FTBFS (does not honor parallel=n in DEB_BUILD_OPTIONS)
Package: src:arpack Version: 3.7.0-1 Severity: serious Tags: ftbfs patch Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:12: installing 'build-aux/compile' configure.ac:17: installing 'build-aux/config.guess' [... snipped ...] make[4]: Leaving directory '/<>/PARPACK/SRC/MPI' Making check in . make[4]: Entering directory '/<>/PARPACK' make[4]: Nothing to be done for 'check-am'. make[4]: Leaving directory '/<>/PARPACK' Making check in TESTS/MPI make[4]: Entering directory '/<>/PARPACK/TESTS/MPI' make issue46 make[5]: Entering directory '/<>/PARPACK/TESTS/MPI' mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -c -o issue46.o issue46.f /bin/bash ../../../libtool --tag=F77 --mode=link mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wl,-z,relro -o issue46 issue46.o ../../../PARPACK/SRC/MPI/libparpack.la -llapack -lblas libtool: link: mpif77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wl,-z -Wl,relro -o .libs/issue46 issue46.o ../../../PARPACK/SRC/MPI/.libs/libparpack.so -llapack -lblas make[5]: Leaving directory '/<>/PARPACK/TESTS/MPI' make check-TESTS make[5]: Entering directory '/<>/PARPACK/TESTS/MPI' make[6]: Entering directory '/<>/PARPACK/TESTS/MPI' FAIL: issue46 Testsuite summary for ARPACK-NG 3.7.0 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See PARPACK/TESTS/MPI/test-suite.log Please report to https://github.com/opencollab/arpack-ng/issues/ make[6]: *** [Makefile:830: test-suite.log] Error 1 make[6]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[5]: *** [Makefile:938: check-TESTS] Error 2 make[5]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[4]: *** [Makefile:1026: check-am] Error 2 make[4]: Leaving directory '/<>/PARPACK/TESTS/MPI' make[3]: *** [Makefile:387: check-recursive] Error 1 make[3]: Leaving directory '/<>/PARPACK' make[2]: *** [Makefile:509: check-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 This used to work ok in all my autobuilders in version 3.5.0+real-2, but it started to fail in some of them in version 3.6.3-1. I've put a bunch of build logs here: https://people.debian.org/~sanvila/build-logs/arpack/ The problem seems to be that the Makefiles wrongly assume that the system has at least 2 CPUs, which may or may not be the case. A simple solution that seems to work is to set 'LOG_FLAGS = -n 1' in both PARPACK/EXAMPLES/MPI/Makefile.am and PARPACK/TESTS/MPI/Makefile.am, but it would be even better to honor parallel=n setting in DEB_BUILD_OPTIONS when there is one, as in the patch below. I did not find a simple way to reproduce this in any system. The usual recipe is to try "taskset -c 0 dpkg-buildpackage" but this does not seem to work here, so if you need a test machine to reproduce the failure please contact me privately and I will gladly provide one. Thanks. --- a/PARPACK/EXAMPLES/MPI/Makefile.am +++ b/PARPACK/EXAMPLES/MPI/Makefile.am @@ -12,7 +12,7 @@ check_PROGRAMS = $(SNDRV) $(DNDRV) $(SSDRV) $(DSDRV) $(CNDRV) $(ZNDRV) # Run MPI tests with "mpirun -n 2" LOG_COMPILER = mpirun -LOG_FLAGS = -n 2 +LOG_FLAGS = -n $(NUMJOBS) TESTS = $(check_PROGRAMS) --- a/PARPACK/TESTS/MPI/Makefile.am +++ b/PARPACK/TESTS/MPI/Makefile.am @@ -3,7 +3,7 @@ LDADD = $(top_builddir)/PARPACK/SRC/MPI/libparpack$(LIBSUFFIX).la $(LAPACK_LIBS) # Run MPI tests with "mpirun -n 2" LOG_COMPILER = mpirun -LOG_FLAGS = -n 2 +LOG_FLAGS = -n $(NUMJOBS) SISS = issue46 --- a/debian/rules +++ b/debian/rules @@ -6,6 +6,12 @@ %: dh $@ +export NUMJOBS = $(shell nproc) + +ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) + NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) +endif + override_dh_auto_configure: # Enforce generic BLAS (to avoid tying to ATLAS
Bug#926215: dune-pdelab: FTBFS with gcc 8.3
Package: src:dune-pdelab Version: 2.6~20180302-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-indep dh binary-indep --parallel --builddirectory=build dh_update_autotools_config -i -O--parallel -O--builddirectory=build debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DBUILD_SHARED_LIBS=1 cd build && 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_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_SHARED_LIBS=1 .. -- The C compiler identification is GNU 8.3.0 -- The CXX compiler identification is GNU 8.3.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features [... snipped ...] cd "/<>/build/dune/pdelab/test" && /usr/bin/c++ -DENABLE_EIGEN=1 -DENABLE_GMP=1 -DENABLE_MPI=1 -DENABLE_SUITESPARSE=1 -DENABLE_SUPERLU=1 -DENABLE_TBB=1 -DENABLE_UG=1 -DHAVE_CONFIG_H -DMPICH_SKIP_MPICXX -DMPIPP_H -DMPI_NO_CPPBIND -DModelP -DUG_USE_NEW_DIMENSION_DEFINES -D_TBB_CPP0X -I"/<>/build" -I"/<>" -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/eigen3 -I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/alberta -std=c++17 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -o CMakeFiles/testdunefunctionsgfs.dir/testdunefunctionsgfs.cc.o -c "/<>/dune/pdelab/test/testdunefunctionsgfs.cc" In file included from /usr/include/dune/istl/paamg/amg.hh:9, from /<>/dune/pdelab/backend/istl/seqistlsolverbackend.hh:15, from /<>/dune/pdelab/backend/istl/istlsolverbackend.hh:6, from /<>/dune/pdelab/backend/istl.hh:7, from /<>/dune/pdelab/backend/istl/dunefunctions.hh:6, from /<>/dune/pdelab/gridfunctionspace/dunefunctionsgridfunctionspace.hh:16, from /<>/dune/pdelab/test/testdunefunctionsgfs.cc:15: /usr/include/dune/istl/paamg/transfer.hh:97:5: error: no declaration matches 'void Dune::Amg::Transfer::prolongateVector(const Dune::Amg::AggregatesMap&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, T, const Dune::Amg::SequentialInformation&, const Redist&)' Transfer::prolongateVector(const AggregatesMap& aggregates, ^~~~ /usr/include/dune/istl/paamg/transfer.hh:62:19: note: candidates are: 'template template static void Dune::Amg::Transfer::prolongateVector(const Dune::Amg::AggregatesMap&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, T1, const Dune::Amg::SequentialInformation&)' static void prolongateVector(const AggregatesMap& aggregates, Vector& coarse, Vector& fine, ^~~~ /usr/include/dune/istl/paamg/transfer.hh:57:19: note: 'template template static void Dune::Amg::Transfer::prolongateVector(const Dune::Amg::AggregatesMap&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, T1, const Dune::Amg::SequentialInformation&, const Redist&)' static void prolongateVector(const AggregatesMap& aggregates, Vector& coarse, Vector& fine, ^~~~ /usr/include/dune/istl/paamg/transfer.hh:50:11: note: 'class Dune::Amg::Transfer' defined here class Transfer ^ /usr/include/dune/istl/paamg/transfer.hh:111:5: error: no declaration matches 'void Dune::Amg::Transfer::prolongateVector(const Dune::Amg::AggregatesMap&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, T, const Dune::Amg::SequentialInformation&)' Transfer::prolongateVector(const AggregatesMap& aggregates, ^~~~ /usr/include/dune/istl/paamg/transfer.hh:62:19: note: candidates are: 'template template static void Dune::Amg::Transfer::prolongateVector(const Dune::Amg::AggregatesMap&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, T1, const Dune::Amg::SequentialInformation&)' static void prolongateVector(const AggregatesMap& aggregates, Vector& coarse, Vector& fine, ^~~~ /usr/include/dune/istl/paamg/transfer.hh:57:19: note: 'template template static void Dune::Amg::Transfer::prolongateVector(const Dune::Amg::AggregatesMap&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, Dune::Amg::Transfer::Vector&, T1, const Dune::Amg::Sequentia
Bug#923607: openblas: FTBFS if CPU is not detected
> Still there seems to be an issue with your specific build environment, > and of course this is a bug (but maybe not an RC one, since you are the > first to report such a build failure after many years). Could you give > more details about the hardware you are using? I'm currently using Scaleway 1-XS and 1-S instances. On both types of instances the package always fail to build. I didn't find a way to move the "unbuildability property" to a non-failing machine (for example, by taking /proc/cpuinfo in the failing machine and using bind-mount on the non-failing machine), so I decided to report it anyway without a "recipe to reproduce it" but with an offer to ssh into a failing machine instead. Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#923607: openblas: FTBFS if CPU is not detected
Package: src:openblas
Version: 0.3.5+ds-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-arch
dh binary-arch
dh_update_autotools_config -a
dh_autoreconf -a
dh_auto_configure -a
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/openblas-0.3.3+ds'
/usr/bin/make NO_LAPACKE=1 NO_AFFINITY=1 USE_OPENMP=0 NO_WARMUP=1
CFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>/openblas-0.3.3+ds=. -fstack-protector-strong
-Wformat -Werror=format-security" FFLAGS="-g -O2
-fdebug-prefix-map=/<>/openblas-0.3.3+ds=. -fstack-protector-strong"
COMMON_OPT= FCOMMON_OPT=-frecursive NUM_THREADS=64 DYNAMIC_ARCH=1
DYNAMIC_OLDER=1
make[2]: Entering directory '/<>/openblas-0.3.3+ds'
getarch_2nd.c: In function 'main':
getarch_2nd.c:12:35: error: 'SGEMM_DEFAULT_UNROLL_M' undeclared (first use in
this function); did you mean 'XGEMM_DEFAULT_UNROLL_M'?
printf("SGEMM_UNROLL_M=%d\n", SGEMM_DEFAULT_UNROLL_M);
^~
XGEMM_DEFAULT_UNROLL_M
getarch_2nd.c:12:35: note: each undeclared identifier is reported only once for
each function it appears in
getarch_2nd.c:13:35: error: 'SGEMM_DEFAULT_UNROLL_N' undeclared (first use in
this function); did you mean 'XGEMM_DEFAULT_UNROLL_N'?
printf("SGEMM_UNROLL_N=%d\n", SGEMM_DEFAULT_UNROLL_N);
^~
XGEMM_DEFAULT_UNROLL_N
getarch_2nd.c:14:35: error: 'DGEMM_DEFAULT_UNROLL_M' undeclared (first use in
this function); did you mean 'XGEMM_DEFAULT_UNROLL_M'?
printf("DGEMM_UNROLL_M=%d\n", DGEMM_DEFAULT_UNROLL_M);
^~
XGEMM_DEFAULT_UNROLL_M
getarch_2nd.c:15:35: error: 'DGEMM_DEFAULT_UNROLL_N' undeclared (first use in
this function); did you mean 'XGEMM_DEFAULT_UNROLL_N'?
printf("DGEMM_UNROLL_N=%d\n", DGEMM_DEFAULT_UNROLL_N);
^~
XGEMM_DEFAULT_UNROLL_N
getarch_2nd.c:19:35: error: 'CGEMM_DEFAULT_UNROLL_M' undeclared (first use in
this function); did you mean 'XGEMM_DEFAULT_UNROLL_M'?
printf("CGEMM_UNROLL_M=%d\n", CGEMM_DEFAULT_UNROLL_M);
^~
XGEMM_DEFAULT_UNROLL_M
getarch_2nd.c:20:35: error: 'CGEMM_DEFAULT_UNROLL_N' undeclared (first use in
this function); did you mean 'XGEMM_DEFAULT_UNROLL_N'?
printf("CGEMM_UNROLL_N=%d\n", CGEMM_DEFAULT_UNROLL_N);
^~
XGEMM_DEFAULT_UNROLL_N
getarch_2nd.c:21:35: error: 'ZGEMM_DEFAULT_UNROLL_M' undeclared (first use in
this function); did you mean 'XGEMM_DEFAULT_UNROLL_M'?
printf("ZGEMM_UNROLL_M=%d\n", ZGEMM_DEFAULT_UNROLL_M);
^~
XGEMM_DEFAULT_UNROLL_M
getarch_2nd.c:22:35: error: 'ZGEMM_DEFAULT_UNROLL_N' undeclared (first use in
this function); did you mean 'XGEMM_DEFAULT_UNROLL_N'?
printf("ZGEMM_UNROLL_N=%d\n", ZGEMM_DEFAULT_UNROLL_N);
^~
XGEMM_DEFAULT_UNROLL_N
getarch_2nd.c:69:50: error: 'SGEMM_DEFAULT_Q' undeclared (first use in this
function); did you mean 'XGEMM_DEFAULT_UNROLL_M'?
printf("#define SLOCAL_BUFFER_SIZE\t%ld\n", (SGEMM_DEFAULT_Q *
SGEMM_DEFAULT_UNROLL_N * 4 * 1 * sizeof(float)));
^~~
XGEMM_DEFAULT_UNROLL_M
getarch_2nd.c:70:50: error: 'DGEMM_DEFAULT_Q' undeclared (first use in this
function); did you mean 'XGEMM_DEFAULT_UNROLL_M'?
printf("#define DLOCAL_BUFFER_SIZE\t%ld\n", (DGEMM_DEFAULT_Q *
DGEMM_DEFAULT_UNROLL_N * 2 * 1 * sizeof(double)));
^~~
XGEMM_DEFAULT_UNROLL_M
getarch_2nd.c:71:50: error: 'CGEMM_DEFAULT_Q' undeclared (first use in this
function); did you mean 'XGEMM_DEFAULT_UNROLL_M'?
printf("#define CLOCAL_BUFFER_SIZE\t%ld\n", (CGEMM_DEFAULT_Q *
CGEMM_DEFAULT_UNROLL_N * 4 * 2 * sizeof(float)));
^~~
XGEMM_DEFAULT_UNROLL_M
getarch_2nd.c:72:50: error: 'ZGEMM_DEFAULT_Q' undeclared (first use in this
function); did you mean 'XGEMM_DEFAULT_UNROLL_M'?
printf("#define ZLOCAL_BUFFER_SIZE\t%ld\n", (ZGEMM_DEFAULT_Q *
ZGEMM_DEFAULT_UNROLL_N * 2 * 2 * sizeof(double)));
^~~
Bug#923466: lammps: FTBFS (dh_auto_configure fails)
Package: src:lammps Version: 0~20181211.gitad1b1897d+dfsg1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --sourcedirectory=cmake --builddirectory=/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build dh_update_autotools_config -i -O--sourcedirectory=cmake -O--builddirectory=/<>/lammps-0\~20181211.gitad1b1897d\+dfsg1/debian/build dh_autoreconf -i -O--sourcedirectory=cmake -O--builddirectory=/<>/lammps-0\~20181211.gitad1b1897d\+dfsg1/debian/build debian/rules override_dh_auto_configure make[1]: Entering directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1' dh_auto_configure -- \ -DPKG_ASPHERE=ON \ -DPKG_BODY=ON \ -DPKG_CLASS2=ON \ -DPKG_COLLOID=ON \ -DPKG_COMPRESS=ON \ -DPKG_CORESHELL=ON \ -DPKG_DIPOLE=ON \ [... snipped ...] Run Build Command:"/usr/bin/make" "cmTC_341b1/fast" make[2]: Entering directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_341b1.dir/build.make CMakeFiles/cmTC_341b1.dir/build make[3]: Entering directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_341b1.dir/feature_tests.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c99 -o CMakeFiles/cmTC_341b1.dir/feature_tests.c.o -c "/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/feature_tests.c" Linking C executable cmTC_341b1 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_341b1.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -rdynamic CMakeFiles/cmTC_341b1.dir/feature_tests.c.o -o cmTC_341b1 make[3]: Leaving directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp' make[2]: Leaving directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp' Feature record: C_FEATURE:1c_function_prototypes Feature record: C_FEATURE:1c_restrict Feature record: C_FEATURE:0c_static_assert Feature record: C_FEATURE:1c_variadic_macros Detecting C [-std=c90] compiler features compiled with the following output: Change Dir: /<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_2dfd2/fast" make[2]: Entering directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_2dfd2.dir/build.make CMakeFiles/cmTC_2dfd2.dir/build make[3]: Entering directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c90 -o CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o -c "/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/feature_tests.c" Linking C executable cmTC_2dfd2 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2dfd2.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -rdynamic CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o -o cmTC_2dfd2 make[3]: Leaving directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp' make[2]: Leaving directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp' Feature record: C_FEATURE:1c_function_prototypes Feature record: C_FEATURE:0c_restrict Feature record: C_FEATURE:0c_static_assert Feature record: C_FEATURE:0c_variadic_macros dh_auto_configure: cd debian/build && 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_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DPKG_ASPHERE=ON -DPKG_BODY=ON -DPKG_CLASS2=ON -DPKG_COLLOID=ON -DPKG_COMPRESS=ON -DPKG_CORESHELL=ON -DPKG_DIPOLE=ON -DPKG_GPU=ON -DPKG_GRANULAR=ON -DPKG_KIM=OFF -DPKG_KSPACE=ON -DPKG_MANYBODY=ON -DPKG_MC=ON -DPKG_MEAM=ON -DPKG_MISC=ON -DPKG_MOLECULE=ON -DPKG_MPIIO=ON -DPKG_OPT=ON -DPKG_PERI=ON -DPKG_POEMS=ON -DPKG_PYTHON=ON -DPKG_QEQ=ON -DPKG_REAX=OFF -DPKG_REPLICA=ON -DPKG_RIGID=ON -DPKG_SHOCK=ON -DPKG_SNAP=ON -DPKG_SRD=ON -DP
Bug#923467: libvigraimpex: FTBFS (Could not import extension sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)
Package: src:libvigraimpex Version: 1.10.0+git20160211.167be93+dfsg1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep make: Nothing to be done for 'build-indep'. fakeroot debian/rules binary-indep dh_testdir dh_testroot /usr/bin/make -f debian/rules doc/vigra/build-stamp make[1]: Entering directory '/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1' mkdir -p obj/ cd obj/ && cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DLIB_SUFFIX="/x86_64-linux-gnu/" -DCMAKE_VERBOSE_MAKEFILE=ON -DWITH_OPENEXR=ON -DCMAKE_C_FLAGS_RELEASE="-g -O2 -fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time -D_FORTIFY_SOURCE=2" -DCMAKE_CXX_FLAGS_RELEASE="-g -O2 -fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time -D_FORTIFY_SOURCE=2" -DCMAKE_SHARED_LINKER_FLAGS_RELEASE="-Wl,-z,relro -Wl,--as-needed -Wl,-z,now" -DPYTHON_EXECUTABLE=/usr/bin/python -DWITH_VIGRANUMPY=0 -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info [... snipped ...] /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1VolumeExportInfo.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1HDF5Handle.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/ErrorReporting.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/group__StandardImageTypes.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/NumericPromotionTraits.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/group__NonLinearDiffusion.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1SIFImportInfo-members.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1GaborFilterFamily-members.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1acc_1_1Central_3_01PowerSum_3_012_01_4_01_4-members.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/Tutorial.html /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/PromoteTraits.html cd /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc && /usr/bin/cmake -E copy_directory /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/documents /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/documents cd /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc && /usr/bin/cmake -E copy_if_different /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/../LICENSE.txt /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/LICENSE.txt cd /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc && /usr/bin/cmake -E copy_if_different /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/../src/matlab/doc/tutorial_reference.pdf /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/documents/tutorial_reference.pdf make[5]: Leaving directory '/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7' [100%] Built target doc_cpp /usr/bin/make -f vigranumpy/docsrc/CMakeFiles/doc_python.dir/build.make vigranumpy/docsrc/CMakeFiles/doc_python.dir/depend make[5]: Entering directory '/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7' cd /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1 /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/vigranumpy/docsrc /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7 /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc/CMakeFiles/doc_python.dir/DependInfo.cmake --color= Scanning dependencies of target doc_python make[5]: Leaving directory '/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7' /usr/bin/make -f vigranumpy/docsrc/CMakeFiles/doc_python.dir/build.make vigranumpy/docsrc/CMakeFiles/doc_python.dir/build make[5]: Entering directory '/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7' [100%] Generating vigranumpy documentation cd /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc && /usr/bin/cmake -E make_directory /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigranumpy cd /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc && /usr/bin/sphinx-build -b html -d /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigranumpy/doctrees -D
Bug#922946: gazebo: please don’t depend on the hinted Roboto fonts
severity 922946 serious thanks On Fri, 22 Feb 2019, Andrej Shadura wrote: > The Roboto upstream no longer provides hinted fonts, so > fonts-roboto-hinted is now a transitional package providing symlinks to > the unhinted fonts. Please modify your package to use the unhinted fonts > instead. The package now FTBFS on buster, for this very same reason I guess. This is what I got today: make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make[3]: *** No rule to make target '/usr/share/fonts/truetype/roboto/hinted/Roboto-Black.ttf', needed by 'gazebo/gui/qrc_resources.cpp'. Stop. Full build log available here: https://people.debian.org/~sanvila/build-logs/gazebo/ Thanks. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#922390: hydroffice.bag: FTBFS (Could not import extension sphinx.ext.pngmath)
Package: src:hydroffice.bag Version: 0.2.15-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build I: pybuild base:217: /usr/bin/python setup.py build running build running build_py creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice copying hydroffice/__init__.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/uncertainty.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/helper.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/__init__.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/base.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/elevation.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/meta.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/bbox.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/tracklist.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag copying hydroffice/bag/bag.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools copying hydroffice/bag/tools/bag_tracklist.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools copying hydroffice/bag/tools/bag_bbox.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools copying hydroffice/bag/tools/bag_elevation.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools copying hydroffice/bag/tools/__init__.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools copying hydroffice/bag/tools/bag_validate.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools copying hydroffice/bag/tools/bag_metadata.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools copying hydroffice/bag/tools/bag_uncertainty.py -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media copying hydroffice/bag/media/favicon.png -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media copying hydroffice/bag/media/hyo_button.png -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media copying hydroffice/bag/media/BAG.ico -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media copying hydroffice/bag/media/BAG.icns -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139 creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag copying hydroffice/bag/iso19139/bag/bagCodelists.xml -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag copying hydroffice/bag/iso19139/bag/extension.xsd -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag copying hydroffice/bag/iso19139/bag/bag.xsd -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco copying hydroffice/bag/iso19139/gco/gcoBase.xsd -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco copying hydroffice/bag/iso19139/gco/basicTypes.xsd -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco copying hydroffice/bag/iso19139/gco/gco.xsd -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco copying hydroffice/bag/iso19139/gco/readme.txt -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gmd copying hydroffice/bag/iso19139/gmd/maintenance.xsd -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gmd copying hydroffice/bag/iso19139/gmd/spatialRepresentation.xsd -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gmd copying hydroffice/bag/iso19139/gmd/dataQuality.xsd -> /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gmd copying hydroffice/bag/iso19139/gmd/metadataApplication.xsd -> /<>/.pybuild/cpython2_2
Bug#922257: pyfr: FTBFS (dh_installman: Could not determine section for ./build/man/_static)
Package: src:pyfr
Version: 1.5.0-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure -i python{version} -p 3.7
I: pybuild base:217: python3.7 setup.py config
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
pybuild --build -i python{version} -p 3.7
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
[... snipped ...]
I: pybuild pybuild:295: mv /<>/debian/tmp/usr/bin/pyfr
/<>/debian/tmp/usr/share/pyfr/run
dh_install -i -O--buildsystem=pybuild
install -d debian/pyfr//usr/share
cp --reflink=auto -a debian/tmp/usr/share/pyfr debian/pyfr//usr/share/
install -d debian/.debhelper/generated/pyfr
install -d debian/.debhelper/generated/pyfr-doc
dh_installdocs -i -O--buildsystem=pybuild
install -d debian/pyfr/usr/share/doc/pyfr
install -p -m0644 debian/copyright
debian/pyfr/usr/share/doc/pyfr/copyright
install -d debian/pyfr-doc/usr/share/doc/pyfr-doc
cd './build/html/..' && find 'html' \( -type f -or -type l \) -and !
-empty -print0 | LC_ALL=C sort -z | xargs -0 -I {} cp --reflink=auto --parents
-dp {} /<>/debian/pyfr-doc/usr/share/doc/pyfr-doc
chown -R 0:0 debian/pyfr-doc/usr/share/doc
chmod -R u\+rw,go=rX debian/pyfr-doc/usr/share/doc
install -p -m0644 debian/copyright
debian/pyfr-doc/usr/share/doc/pyfr-doc/copyright
install -d debian/pyfr-doc/usr/share/doc-base/
install -p -m0644 debian/pyfr-doc.doc-base
debian/pyfr-doc/usr/share/doc-base/pyfr-doc
rm -f debian/pyfr-doc.debhelper.log debian/pyfr.debhelper.log
debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/<>'
dh_sphinxdoc --exclude=MathJax.js
ln -sf ../../../../javascript/sphinxdoc/1.0/sidebar.js
debian/pyfr-doc/usr/share/doc/pyfr-doc/html/_static/sidebar.js
ln -sf ../../../../javascript/sphinxdoc/1.0/underscore.js
debian/pyfr-doc/usr/share/doc/pyfr-doc/html/_static/underscore.js
ln -sf ../../../../javascript/sphinxdoc/1.0/jquery.js
debian/pyfr-doc/usr/share/doc/pyfr-doc/html/_static/jquery.js
ln -sf ../../../../javascript/sphinxdoc/1.0/doctools.js
debian/pyfr-doc/usr/share/doc/pyfr-doc/html/_static/doctools.js
ln -sf ../../../../javascript/sphinxdoc/1.0/searchtools.js
debian/pyfr-doc/usr/share/doc/pyfr-doc/html/_static/searchtools.js
rm -rf debian/pyfr-doc/usr/share/doc/pyfr-doc/html/.doctrees
rm -f debian/pyfr-doc/usr/share/doc/pyfr-doc/html/.buildinfo
rm -f debian/pyfr-doc/usr/share/doc/pyfr-doc/html/_static/websupport.js
(grep -a -s -v sphinxdoc:Depends debian/pyfr-doc.substvars; echo
"sphinxdoc:Depends=libjs-sphinxdoc (>= 1.0)") > debian/pyfr-doc.substvars.new
mv debian/pyfr-doc.substvars.new debian/pyfr-doc.substvars
(grep -a -s -v sphinxdoc:Built-Using debian/pyfr-doc.substvars; echo
"sphinxdoc:Built-Using=sphinx (= 1.8.3-2)") > debian/pyfr-doc.substvars.new
mv debian/pyfr-doc.substvars.new debian/pyfr-doc.substvars
make[1]: Leaving directory '/<>'
dh_installchangelogs -i -O--buildsystem=pybuild
install -p -m0644 debian/changelog
debian/pyfr/usr/share/doc/pyfr/changelog.Debian
install -p -m0644 debian/changelog
debian/pyfr-doc/usr/share/doc/pyfr-doc/changelog.Debian
dh_installexamples -i -O--buildsystem=pybuild
install -d debian/pyfr-doc/usr/share/doc/pyfr-doc/examples
cp --reflink=auto -a ./examples/couette_flow_2d
debian/pyfr-doc/usr/share/doc/pyfr-doc/examples
cp --reflink=auto -a ./examples/euler_vortex_2d
debian/pyfr-doc/usr/share/doc/pyfr-doc/examples
dh_installman -i -O--buildsystem=pybuild
dh_installman: Could not determine section for ./build/man/_static
dh_installman: Aborting due to earlier error
make: *** [debian/rules:12: binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyfr.html
where you can get a full build log if you need it.
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.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
Bug#921979: lmfit-py: FTBFS randomly (test_covariance_matrix.test_bounded_parameters fails)
Package: src:lmfit-py Version: 0.9.11+dfsg-1 Severity: serious Tags: ftbfs patch Hello Andreas et al. I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>/lmfit-py-0.9.11+dfsg' dh_auto_build I: pybuild base:217: /usr/bin/python setup.py build running build running build_py creating /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/lineshapes.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/models.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/jsonutils.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/__init__.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/printfuncs.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/_ampgo.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/model.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/minimizer.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/parameter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/confidence.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit copying lmfit/_version.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit creating /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/ui copying lmfit/ui/__init__.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/ui copying lmfit/ui/ipy_fitter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/ui copying lmfit/ui/basefitter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/ui UPDATING /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/_version.py set /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build/lmfit/_version.py to '0.9.11' I: pybuild pybuild:295: cp -r NIST_STRD /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython2_2.7_lmfit/build I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py creating /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/lineshapes.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/models.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/jsonutils.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/__init__.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/printfuncs.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/_ampgo.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/model.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/minimizer.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/parameter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/confidence.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit copying lmfit/_version.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit creating /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/ui copying lmfit/ui/__init__.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/ui copying lmfit/ui/ipy_fitter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/ui copying lmfit/ui/basefitter.py -> /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/ui UPDATING /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/_version.py set /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build/lmfit/_version.py to '0.9.11' I: pybuild pybuild:295: cp -r NIST_STRD /<>/lmfit-py-0.9.11+dfsg/.pybuild/cpython3_3.7_lmfit/build PYTHONPATH=. http_proxy='localhost' sphinx-build -N -bhtml doc/ build/html # HTML generator Running Sphinx v1.7.9 making output directory... loading pickled environment... not yet created loading intersphinx inventory from https://docs.python.org/2/objects.inv... loading intersphinx inventory from https://docs.scipy.org/doc/numpy/objects.inv... loading intersphinx inventory from https://docs.scipy.org/doc/scipy/reference/objects.inv... building [mo]: targets for 0 po files that are out of date building [html]: target
Bug#921897: morse-simulator: FTBFS (Could not import extension sphinx.ext.pngmath)
Package: src:morse-simulator Version: 1.4-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python3 dh_update_autotools_config -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DBUILD_DOC_SUPPORT=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 \ -DCPACK_DEBIAN_PACKAGE_DEPENDS=python3-all-dev -DPYMORSE_SUPPORT=ON cd obj-x86_64-linux-gnu && 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_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_DOC_SUPPORT=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 -DCPACK_DEBIAN_PACKAGE_DEPENDS=python3-all-dev -DPYMORSE_SUPPORT=ON .. -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done [... snipped ...] CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_SYSCONFDIR CPACK_DEBIAN_PACKAGE_DEPENDS -- Build files have been written to: /<>/obj-x86_64-linux-gnu make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' cp version.py obj-*/ dh_auto_build cd obj-x86_64-linux-gnu && make -j1 make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/depend make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/man.dir/DependInfo.cmake --color= Scanning dependencies of target man make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/build make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' env PYTHONPATH=/<>/obj-x86_64-linux-gnu:/<>/obj-x86_64-linux-gnu/src:/<>/obj-x86_64-linux-gnu/fakeenv:/<>/src:/<>/testing:/<>/bindings/pymorse/src/:$PYTHONPATH PYTHONDONTWRITEBYTECODE="morse" MORSESOURCE=/<> /usr/bin/python3 /usr/bin/sphinx-build -b man -c /<>/obj-x86_64-linux-gnu/doc /<>/doc/man /<>/obj-x86_64-linux-gnu/doc/man && /bin/gzip -f /<>/obj-x86_64-linux-gnu/doc/man/*.1 Running Sphinx v1.8.3 Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named 'sphinx.ext.pngmath') make[4]: *** [CMakeFiles/man.dir/build.make:60: CMakeFiles/man] Error 2 make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** [CMakeFiles/Makefile2:140: CMakeFiles/man.dir/all] Error 2 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [Makefile:144: all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2 make[1]: *** [debian/rules:27: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/morse-simulator.html where you can get a full build log if you need it. 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. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#921838: ppl: FTBFS (LaTeX error)
Package: src:ppl
Version: 1:1.2-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:152: installing './compile'
configure.ac:43: installing './missing'
[... snipped ...]
d on input line 40.
) (./group__PPL__C__interface.tex)
Underfull \vbox (badness 7740) has occurred while \output is active [17]
[18] (./group__Init.tex
Underfull \hbox (badness 1) detected at line 35
[][][]
Underfull \hbox (badness 1) detected at line 48
[][][]
[19]) [20] (./group__Version.tex [21]) [22] (./group__Error.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/omsptm.fd)
Overfull \hbox (1.62299pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]O[]U[]T[][][][]O[]F[][]
[][]M[]E[]M[]O[]RY[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]V[]A[]L[]
I[]D[][][][]A[]R[]G[]U[]M[]E[]NT[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]D
[]O[]M[]
Overfull \hbox (1.35289pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]A[]R[]I[]T[]H[]M[]E[]T[]I[]C[][][][]O[]V[]E[
]R[]F[]L[]OW[][], [][]P[]P[]L[][][][]S[]T[]D[]I[]O[][][][]E[]R[]R[]OR[][], [][]
P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]T[]E[]R[]N[]A[]L[][][][]E[]R[]R[]OR[]
[], [][]P[]
! Missing } inserted.
}
l.88 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.88 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/doc/user-configured-c-interface.latex-dir'
make[2]: *** [Makefile:2064: ppl-user-configured-c-interface-1.2.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
dh_auto_build: cd doc && make -j1 user-configured returned exit code 2
make[1]: *** [debian/rules:75: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:52: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html
where you can get a full build log if you need it.
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.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#921802: primesieve: FTBFS (LaTeX error)
Package: src:primesieve
Version: 7.3+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --builddirectory=_build
dh_update_autotools_config -i -O--builddirectory=_build
dh_autoreconf -i -O--builddirectory=_build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/primesieve-7.3+ds'
dh_auto_configure -- \
-DBUILD_TESTS=ON \
-DBUILD_EXAMPLES=ON \
-DBUILD_DOC=ON
cd _build && 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_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTS=ON
-DBUILD_EXAMPLES=ON -DBUILD_DOC=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
[... snipped ...]
LaTeX Warning: Reference `iterator_8h' on page 9 undefined on input line 3.
LaTeX Warning: Reference `iterator_8hpp' on page 9 undefined on input line 4.
LaTeX Warning: Reference `primesieve_8h' on page 9 undefined on input line 5.
LaTeX Warning: Reference `primesieve_8hpp' on page 9 undefined on input line 6.
LaTeX Warning: Reference `primesieve__error_8hpp' on page 9 undefined on input
line 7.
) [9] [10]
Chapter 6.
(./namespaceprimesieve.tex [11]
Underfull \hbox (badness 1) detected at line 94
[][][]
[12] [13]
Underfull \hbox (badness 1) detected at line 156
[][][]
! Missing } inserted.
}
l.175 \end{DoxyParams}
?
! Emergency stop.
}
l.175 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/primesieve-7.3+ds/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:15: doc] Error 2
make[2]: Leaving directory '/<>/primesieve-7.3+ds'
make[1]: *** [debian/rules:33: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/primesieve-7.3+ds'
make: *** [debian/rules:24: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/primesieve.html
where you can get a full build log if you need it.
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.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#921807: sketch: FTBFS (LaTeX error)
Package: src:sketch Version: 1:0.3.7-10 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' perl makever.pl not generating web page make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build make -j1 make[2]: Entering directory '/<>' [... snipped ...] (/usr/share/texlive/texmf-dist/tex/generic/pst-node/pst-node.tex))) (/usr/share/texlive/texmf-dist/tex/latex/pst-text/pst-text.sty (/usr/share/texlive/texmf-dist/tex/generic/pst-text/pst-text.tex v1.01, 2018/12/22(tvz,hv))) (/usr/share/texlive/texmf-dist/tex/latex/pst-3d/pst-3d.sty (/usr/share/texlive/texmf-dist/tex/generic/pst-3d/pst-3d.tex)) (/usr/share/texlive/texmf-dist/tex/latex/pst-eps/pst-eps.sty (/usr/share/texlive/texmf-dist/tex/generic/pst-eps/pst-eps.tex v1.00, 2006/11/04)) (/usr/share/texlive/texmf-dist/tex/latex/pst-fill/pst-fill.sty (/usr/share/texlive/texmf-dist/tex/generic/pst-fill/pst-fill.tex `PST-Fill' v1.01, 2007/03/10 (tvz,dg,hv))) (/usr/share/texlive/texmf-dist/tex/latex/pstricks-add/pstricks-add.sty (/usr/share/texlive/texmf-dist/tex/latex/pst-math/pst-math.sty (/usr/share/texlive/texmf-dist/tex/latex/pst-calculate/pst-calculate.sty (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex) (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3dvips.def))) (/usr/share/texlive/texmf-dist/tex/latex/siunitx/siunitx.sty (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty)) (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty) (/usr/share/texlive/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e.sty) (/usr/share/texlive/texmf-dist/tex/latex/translator/translator.sty))) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty) ! LaTeX Error: File `xstring.sty' not found. Type X to quit or to proceed, or enter new name. (Default extension: sty) Enter file name: ! Emergency stop. l.19 \input pst-math.tex^^M No pages of output. Transcript written on ex000-tmp.log. Inappropriate ioctl for device at make.pl line 34, line 1. make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:21: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sketch.html where you can get a full build log if you need it. 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. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#921786: kim-api: FTBFS (F90-F-0000-Internal compiler error. process_formal_arguments: Function argument with mismatched size that is neither integer nor floating-point)
Package: src:kim-api Version: 2.0~beta2.gita734d1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' mkdir -p /<>/debian/home dh_auto_configure -- -DKIM_API_BUILD_MODELS_AND_DRIVERS=ON cd obj-x86_64-linux-gnu && 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_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DKIM_API_BUILD_MODELS_AND_DRIVERS=ON .. -- The CXX compiler identification is GNU 8.2.0 -- The C compiler identification is GNU 8.2.0 -- The Fortran compiler identification is Flang 99.99.1 -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works [... snipped ...] /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_length_unit_f.f90.o.provides.build [ 24%] Building Fortran object CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o /usr/bin/f95 -Dkim_api_EXPORTS -I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" -I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" -I"/<>/c/include" -I"/<>/cpp/src" -I"/<>/fortran/include" -std=f2003 -Wall -Wextra -pedantic -ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -JFortran_MODULES -fPIC -c "/<>/fortran/src/kim_log_f.f90" -o CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o flang: warning: argument unused during compilation: '-ffree-line-length-none' [-Wunused-command-line-argument] /usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_log_f_module.mod CMakeFiles/kim-api.dir/kim_log_f_module.mod.stamp Flang /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o.provides.build [ 25%] Building Fortran object CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o /usr/bin/f95 -Dkim_api_EXPORTS -I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" -I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" -I"/<>/c/include" -I"/<>/cpp/src" -I"/<>/fortran/include" -std=f2003 -Wall -Wextra -pedantic -ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -JFortran_MODULES -fPIC -c "/<>/fortran/src/kim_log_verbosity_f.f90" -o CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o flang: warning: argument unused during compilation: '-ffree-line-length-none' [-Wunused-command-line-argument] /usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_log_verbosity_f_module.mod CMakeFiles/kim-api.dir/kim_log_verbosity_f_module.mod.stamp Flang /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o.provides.build [ 25%] Building Fortran object CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o /usr/bin/f95 -Dkim_api_EXPORTS -I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" -I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" -I"/<>/c/include" -I"/<>/cpp/src" -I"/<>/fortran/include" -std=f2003 -Wall -Wextra -pedantic -ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -JFortran_MODULES -fPIC -c "/<>/fortran/src/kim_model_compute_arguments_create_f.f90" -o CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o flang: warning: argument unused during compilation: '-ffree-line-length-none' [-Wunused-command-line-argument] /usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_model_compute_arguments_create_f_module.mod CMakeFiles/kim-api.dir/kim_model_compute_arguments_create_f_module.mod.stamp Flang /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o.provides.build [ 26%] Building Fortran object CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_destroy_f.f90.o /usr/bin/f95 -Dkim_api_EXPORTS -I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" -I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" -I"/<>/c/include" -I"/<>/cpp/src" -I"/<>/fortran/include" -std=f2003 -Wall -Wextra -pedantic -ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -JFortran_MODULES -fPIC -c "/<>/fortran/src/kim_model_compute_arguments_destroy_f.f90" -o CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_destroy_f.f90.o flang: warning: argument unused during compilation: '-ffree-line-length-none' [-Wunused-command-line-argument] /usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_model_compute_arguments_destroy_f_module.mod CMakeFiles/kim-api.dir/kim_model_compute_arguments_destroy_f_module.mod.stamp Flang /usr/bin/cmake -E touch CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_destroy_f.f90.o.provide
Bug#921776: bliss: FTBFS (LaTeX error)
Package: src:bliss
Version: 0.73-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with autoreconf --builddirectory=_build --parallel
dh_update_autotools_config -i -O--builddirectory=_build -O--parallel
dh_autoreconf -i -O--builddirectory=_build -O--parallel
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:19: installing 'build-aux/compile'
configure.ac:16: installing 'build-aux/config.guess'
[... snipped ...]
Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
lookup cache used 185/65536 hits=1285 misses=221
finished...
cd /<>/_build/DEBIAN/doc/html && { \
rm -f *.md5 jquery.js ; \
rdfind -outputname /dev/null -makesymlinks true . ; \
symlinks -r -c -s -v . ; \
ln -sf /usr/share/javascript/jquery/jquery.js ; \
}
Now scanning ".", found 60 files.
Now have 60 files in total.
Removed 0 files due to nonunique device and inode.
Total size is 384954 bytes or 376 KiB
Removed 60 files due to unique sizes from list.0 files left.
Now eliminating candidates based on first bytes:removed 0 files from list.0
files left.
Now eliminating candidates based on last bytes:removed 0 files from list.0
files left.
Now eliminating candidates based on sha1 checksum:removed 0 files from list.0
files left.
It seems like you have 0 files that are not unique
Totally, 0 B can be reduced.
Now making results file /dev/null
Now making symbolic links. creating
Making 0 links.
cd /<>/_build/DEBIAN/doc/latex && { \
make && mv refman.pdf bliss_refman.pdf ; \
}
make[3]: Entering directory '/<>/_build/DEBIAN/doc/latex'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl
refman.pdf
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2018-12-01>
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory '/<>/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:30: doc] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:16: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bliss.html
where you can get a full build log if you need it.
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.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
