Source: bookletimposer
Version: 0.2-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Due to the recent switch of pandoc data files to his own package
named pandoc-data.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2
>    dh_testdir
>    dh_auto_configure
>    dh_auto_build
> running build
> running build_uiheaders
> intltool-extract --type=gettext/glade data/bookletimposer.ui
> Generating C format header file for translation.
> Wrote data/bookletimposer.ui.h
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> copying lib/pdfimposer.py -> build/lib.linux-x86_64-2.7
> creating build/lib.linux-x86_64-2.7/bookletimposer
> copying lib/bookletimposer/gui.py -> build/lib.linux-x86_64-2.7/bookletimposer
> copying lib/bookletimposer/config.py -> 
> build/lib.linux-x86_64-2.7/bookletimposer
> copying lib/bookletimposer/__init__.py -> 
> build/lib.linux-x86_64-2.7/bookletimposer
> copying lib/bookletimposer/backend.py -> 
> build/lib.linux-x86_64-2.7/bookletimposer
> running build_scripts
> creating build/scripts-2.7
> copying and adjusting bin/bookletimposer -> build/scripts-2.7
> changing mode of build/scripts-2.7/bookletimposer from 664 to 775
> running build_man
> pandoc -s -t man -o build/man/bookletimposer.1 doc/bookletimposer.1.mdwn
> pandoc: /usr/share/pandoc/data/templates/default.man: openBinaryFile: does 
> not exist (No such file or directory)
> error: command 'pandoc' failed with exit status 1
> dh_auto_build: python setup.py build --force returned exit code 1
> make: *** [build] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/09/22/bookletimposer_0.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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to