Source: spellutils Version: 0.7-8 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh_testdir > touch ./config.rpath > dh_autoreconf > aclocal: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer > supported. > configure.in:26: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd > /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from... > configure.in:26: the top level > ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer > supported. > configure.in:26: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd > aclocal.m4:77: AM_GNU_GETTEXT is expanded from... > configure.in:26: the top level > autoreconf: configure.in: AM_GNU_GETTEXT is used, but not > AM_GNU_GETTEXT_VERSION > ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer > supported. > configure.in:26: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd > aclocal.m4:77: AM_GNU_GETTEXT is expanded from... > configure.in:26: the top level > configure:4772: error: possibly undefined macro: AM_INTL_SUBDIR > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > autoreconf: /usr/bin/autoconf failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:55: configure-stamp] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/12/26/spellutils_0.7-8_unstable.log 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 marking 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 me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.