Bug#713209: libmpc: FTBFS: /bin/sh: 1: aclocal-1.11: not found

Lucas Nussbaum lucas at lucas-nussbaum.net
Sat Jun 22 12:06:25 UTC 2013


Source: libmpc
Version: 2:0.1~r459-4
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
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
> test -x debian/rules
> mkdir -p "."
> 
> WARNING: copyright-check disabled - touch debian/copyright_hints to enable.
> 
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> if test -e /usr/share/misc/config.guess ; then \
> 		for i in ./config/config.guess ; do \
> 			if ! test -e $i.cdbs-orig ; then \
> 				mv $i $i.cdbs-orig ; \
> 				cp --remove-destination /usr/share/misc/config.guess $i ; \
> 			fi ; \
> 		done ; \
> 	fi
> if test -e /usr/share/misc/config.sub ; then \
> 		for i in ./config/config.sub ; do \
> 			if ! test -e $i.cdbs-orig ; then \
> 				mv $i $i.cdbs-orig ; \
> 				cp --remove-destination /usr/share/misc/config.sub $i ; \
> 			fi ; \
> 		done ; \
> 	fi
> cd . && libtoolize -c -f
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'.
> libtoolize: copying file `config/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> cd . && aclocal-1.11 -I m4
> /bin/sh: 1: aclocal-1.11: not found
> make: *** [debian/stamp-autotools-files] Error 127

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/libmpc_0.1~r459-4_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.



More information about the pkg-multimedia-maintainers mailing list