Source: lbcd Version: 3.4.1-2 Severity: serious Tags: jessie sid User: [email protected] Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > debian/rules build > dh build --parallel --with autoreconf > dh_testdir -O--parallel > dh_autoreconf -O--parallel > automake: warnings are treated as errors > /usr/share/automake-1.13/am/library.am: warning: 'modules/libmodules.a': > linking libraries using a non-POSIX > /usr/share/automake-1.13/am/library.am: archiver requires 'AM_PROG_AR' in > 'configure.ac' > Makefile.am:18: while processing library 'modules/libmodules.a' > /usr/share/automake-1.13/am/library.am: warning: 'portable/libportable.a': > linking libraries using a non-POSIX > /usr/share/automake-1.13/am/library.am: archiver requires 'AM_PROG_AR' in > 'configure.ac' > Makefile.am:18: while processing library 'portable/libportable.a' > /usr/share/automake-1.13/am/library.am: warning: 'tests/tap/libtap.a': > linking libraries using a non-POSIX > /usr/share/automake-1.13/am/library.am: archiver requires 'AM_PROG_AR' in > 'configure.ac' > Makefile.am:86: while processing library 'tests/tap/libtap.a' > /usr/share/automake-1.13/am/library.am: warning: 'util/libutil.a': linking > libraries using a non-POSIX > /usr/share/automake-1.13/am/library.am: archiver requires 'AM_PROG_AR' in > 'configure.ac' > Makefile.am:18: while processing library 'util/libutil.a' > autoreconf: automake failed with exit status: 1 > dh_autoreconf: autoreconf -f -i returned exit code 1 > make: *** [build] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/lbcd_3.4.1-2_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! 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. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
