Source: am-utils
Version: 6.2+rc20110530-3
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:
> make[3]: Entering directory 
> `/«BUILDDIR»/am-utils-6.2+rc20110530/A.x86_64-unknown-linux-deb/doc'
> Updating ../../doc/version.texi
> restore=: && backupdir=".am$$" && \
>       am__cwd=`pwd` && cd ../../doc && \
>       rm -rf $backupdir && mkdir $backupdir && \
>       if (/bin/bash /«BUILDDIR»/am-utils-6.2+rc20110530/missing --run 
> makeinfo --version) >/dev/null 2>&1; then \
>         for f in ../../doc/am-utils.info ../../doc/am-utils.info-[0-9] 
> ../../doc/am-utils.info-[0-9][0-9] ../../doc/am-utils.i[0-9] 
> ../../doc/am-utils.i[0-9][0-9]; do \
>           if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
>         done; \
>       else :; fi && \
>       cd "$am__cwd"; \
>       if /bin/bash /«BUILDDIR»/am-utils-6.2+rc20110530/missing --run makeinfo 
>   -I ../../doc \
>        -o ../../doc/am-utils.info ../../doc/am-utils.texi; \
>       then \
>         rc=0; \
>         cd ../../doc; \
>       else \
>         rc=$?; \
>         cd ../../doc && \
>         $restore $backupdir/* `echo "./../../doc/am-utils.info" | sed 
> 's|[^/]*$||'`; \
>       fi; \
>       rm -rf $backupdir; exit $rc
> ../../doc/am-utils.texi:70: @sp missing argument
> make[3]: *** [../../doc/am-utils.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/am-utils_6.2+rc20110530-3_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