Source: libqtdbusmock Version: 0.9.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu' > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends > "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/tests > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/tests > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/DependInfo.cmake > "--color=" > make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu' > make -f tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build.make > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build > make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu' > make[3]: *** No rule to make target 'tests/gmock/lib/libgmock_main.a', needed > by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop. > make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:337: > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/libqtdbusmock_0.9.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&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.
