Source: dvdbackup
Version: 0.4.2-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
> Copying file m4/codeset.m4
> Copying file m4/glibc2.m4
> Copying file m4/glibc21.m4
> Copying file m4/intdiv0.m4
> Copying file m4/intl.m4
> Copying file m4/intldir.m4
> Copying file m4/intmax.m4
> Copying file m4/inttypes-pri.m4
> Copying file m4/inttypes_h.m4
> Copying file m4/lcmessage.m4
> Copying file m4/lock.m4
> Copying file m4/longlong.m4
> Copying file m4/printf-posix.m4
> Copying file m4/size_max.m4
> Copying file m4/stdint_h.m4
> Copying file m4/uintmax_t.m4
> Copying file m4/visibility.m4
> Copying file m4/wchar_t.m4
> Copying file m4/wint_t.m4
> Copying file m4/xsize.m4
> Copying file po/Makevars.template
> automake: warnings are treated as errors
> configure.ac:19: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its 
> use is discouraged.
> configure.ac:19: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro 
> instead,
> configure.ac:19: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your 
> Makefile.am files.
> 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/dvdbackup_0.4.2-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]

Reply via email to