Source: speech-dispatcher
Version: 0.7.1-6.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:
> make[3]: Entering directory `/«PKGBUILDDIR»/doc'
> Updating ./version.texi
> restore=: && backupdir=".am$$" && \
>       am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
>       rm -rf $backupdir && mkdir $backupdir && \
>       if (/bin/bash /«PKGBUILDDIR»/missing makeinfo --version) >/dev/null 
> 2>&1; then \
>         for f in speech-dispatcher.info speech-dispatcher.info-[0-9] 
> speech-dispatcher.info-[0-9][0-9] speech-dispatcher.i[0-9] 
> speech-dispatcher.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 /«PKGBUILDDIR»/missing makeinfo   -I . \
>        -o speech-dispatcher.info speech-dispatcher.texi; \
>       then \
>         rc=0; \
>         CDPATH="${ZSH_VERSION+.}:" && cd .; \
>       else \
>         rc=$?; \
>         CDPATH="${ZSH_VERSION+.}:" && cd . && \
>         $restore $backupdir/* `echo "./speech-dispatcher.info" | sed 
> 's|[^/]*$||'`; \
>       fi; \
>       rm -rf $backupdir; exit $rc
> ./fdl.texi:404: raising the section level of @appendixsubsec which is too low
> make[3]: *** [speech-dispatcher.info] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/speech-dispatcher_0.7.1-6.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