Package: bum
Version: 2.5.0-1
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20090620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> [ ! -f Makefile ] || /usr/bin/make clean
> rm -f config.log config.status
> rm -f po/*.gmo
> dh_clean 
>  dpkg-source -b bum-2.5.0
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building bum using existing bum_2.5.0.orig.tar.gz
> dpkg-source: info: building bum in bum_2.5.0-1.diff.gz
> dpkg-source: info: building bum in bum_2.5.0-1.dsc
>  debian/rules build
> dh_testdir
> CFLAGS="-Wall -g -O2" \
>               ./configure \
>                       --host=x86_64-linux-gnu \
>                       --build=x86_64-linux-gnu \
>                       --prefix=/usr \
>                       --mandir=\${prefix}/share/man \
>                       --infodir=\${prefix}/share/info
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for style of include used by make... GNU
> checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... 
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether x86_64-linux-gnu-gcc accepts -g... yes
> checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
> checking dependency style of x86_64-linux-gnu-gcc... none
> checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking locale.h usability... yes
> checking locale.h presence... yes
> checking for locale.h... yes
> checking for LC_MESSAGES... yes
> checking libintl.h usability... yes
> checking libintl.h presence... yes
> checking for libintl.h... yes
> checking for ngettext in libc... yes
> checking for dgettext in libc... yes
> checking for bind_textdomain_codeset... yes
> checking for msgfmt... /usr/bin/msgfmt
> checking for dcgettext... yes
> checking if msgfmt accepts -c... yes
> checking for gmsgfmt... /usr/bin/msgfmt
> checking for xgettext... /usr/bin/xgettext
> checking for catalogs to be installed...  it de es fr ko mk nb nl pl ru tr he 
> ka sv
> checking whether NLS is requested... yes
> checking for intltool-update... no
> checking for intltool-merge... no
> checking for intltool-extract... no
> configure: error: The intltool scripts were not found. Please install 
> intltool.
> make: *** [configure-stamp] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/06/20/bum_2.5.0-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to