Source: ros-actionlib Version: 1.14.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/actionlib' > make[4]: Nothing to be done for 'CMakeFiles/run_tests.dir/build'. > make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/actionlib' > [100%] Built target run_tests > make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/actionlib' > /usr/bin/cmake -E cmake_progress_start > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/actionlib/CMakeFiles 0 > make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/actionlib' > make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/actionlib' > catkin_test_results > obj-x86_64-linux-gnu/actionlib/test_results/actionlib/rosunit-test_cpp_simple_client.xml: > 14 tests, 0 errors, 2 failures, 0 skipped > Summary: 75 tests, 0 errors, 2 failures, 0 skipped > dh_auto_install: error: rosbuilder --sourcedir . --builddir > obj-x86_64-linux-gnu --destdir /<<PKGBUILDDIR>>/debian/tmp returned exit code > 1 > make: *** [debian/rules:11: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/01/01/ros-actionlib_1.14.0-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
