Source: japi-compliance-checker Version: 2.4-3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild
Hi, This package fails to do build a binary-only build (not source) after a successful build (dpkg-buildpackage ; dpkg-buildpackage -b). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild Relevant part of the build log: > cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -b > --------------------------------------------------------------------------------------------------------------------------------------------------- > > dpkg-buildpackage: info: source package japi-compliance-checker > dpkg-buildpackage: info: source version 2.4-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by tony mancill <tmanc...@debian.org> > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean > dh_auto_clean > make -j8 clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > echo "Nothing to clean up." > Nothing to clean up. > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_clean > rm -f debian/debhelper-build-stamp > rm -rf debian/.debhelper/ > rm -f debian/japi-compliance-checker.debhelper.log > rm -f -- debian/japi-compliance-checker.substvars debian/files > rm -fr -- debian/japi-compliance-checker/ debian/tmp/ > find . \( \( \ > \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path > .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o > -type f -a \ > \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \ > -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \ > -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \ > -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \ > \) -exec rm -f {} + \) -o \ > \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) > \) > debian/rules binary > dh binary > dh_update_autotools_config > dh_autoreconf > dh_auto_configure > debian/rules override_dh_auto_build > make[1]: Entering directory '/<<PKGBUILDDIR>>' > # remove '.pl' from the generated man page by help2man: > ln japi-compliance-checker.pl japi-compliance-checker > ln: failed to create hard link 'japi-compliance-checker': File exists > make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > make: *** [debian/rules:6: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > > E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -b' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/16/japi-compliance-checker_2.4-3_unstable.log 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. __ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
