Source: logol Version: 1.6.9-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131128 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory `/«PKGBUILDDIR»' > dh_install > rm -f debian/logol/usr/share/logol/prolog/*.c > rm -f debian/logol/usr/share/logol/prolog/*.exe > rm -f debian/logol/usr/share/logol/prolog/logol.properties > rm -f debian/logol/usr/share/logol/tools/*.keep_old_script > if [ -e debian/logol ]; then chmod -f 755 debian/logol/usr/share/logol/*.sh; > fi > if [ -e debian/logol ]; then chmod -f 755 > debian/logol/usr/share/logol/tools/*.sh; fi > if [ -e debian/logol ]; then chmod -f 755 > debian/logol/usr/share/logol/tools/*.rb; fi > if [ -e debian/logol ]; then chmod -f 755 > debian/logol/usr/share/logol/tools/mycostfunction; fi > make[1]: Leaving directory `/«PKGBUILDDIR»' > dh_installdocs > cp: cannot stat 'Doc/logolParser.pdf': No such file or directory > dh_installdocs: cp -a Doc/logolParser.pdf debian/logol/usr/share/doc/logol > returned exit code 1 > make: *** [binary] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/11/28/logol_1.6.9-1_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
