Source: mecab-naist-jdic Version: 0.6.3.b-20111013-11 Severity: minor Tags: trixie sid ftbfs User: [email protected] Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: [email protected] 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 mecab-naist-jdic > dpkg-buildpackage: info: source version 0.6.3.b-20111013-11 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Hideki Yamane <[email protected]> > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > fakeroot debian/rules clean > dh clean > dh_auto_clean > make -j8 distclean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > test -z "matrix.bin char.bin sys.dic unk.dic" || rm -f matrix.bin char.bin > sys.dic unk.dic > test -z "" || rm -f > test . = "." || test -z "" || rm -f > rm -f config.status config.cache config.log configure.lineno > config.status.lineno > rm -f Makefile > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_autoreconf_clean > debian/rules override_dh_clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > rm /<<PKGBUILDDIR>>/{config.log,config.status,*.dic,*.bin,ChangeLog.orig} > rm: cannot remove > '/<<PKGBUILDDIR>>/{config.log,config.status,*.dic,*.bin,ChangeLog.orig}': No > such file or directory > make[1]: [debian/rules:11: override_dh_clean] Error 1 (ignored) > dh_clean > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > debian/rules build > dh build > dh_update_autotools_config > dh_autoreconf > autoreconf: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > aclocal: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are > deprecated. > ./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from... > aclocal.m4:139: AM_INIT_AUTOMAKE is expanded from... > configure.in:2: the top level > configure.in:57: warning: AC_OUTPUT should be used without arguments. > configure.in:57: You should run autoupdate. > automake: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are > deprecated. For more info, see: > configure.in:2: > https://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation > configure.in:2: installing './install-sh' > configure.in:2: installing './missing' > Makefile.am: error: required file './ChangeLog' not found > Makefile.am: installing './INSTALL' > automake: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > autoreconf: error: automake failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:8: build] Error 25 > dpkg-buildpackage: error: debian/rules build 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/mecab-naist-jdic_0.6.3.b-20111013-11_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.
