Source: suricata Version: 1.2.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: > make[3]: Entering directory `/«PKGBUILDDIR»' > make[3]: Nothing to be done for `install-exec-am'. > make[3]: Nothing to be done for `install-data-am'. > make[3]: Leaving directory `/«PKGBUILDDIR»' > make[2]: Leaving directory `/«PKGBUILDDIR»' > make[1]: Leaving directory `/«PKGBUILDDIR»' > dh_install -a > cp -a debian/tmp/suricata-debian.yaml debian/suricata//etc/suricata/ > cp: cannot stat `debian/tmp/suricata-debian.yaml': No such file or directory > dh_install: cp -a debian/tmp/suricata-debian.yaml > debian/suricata//etc/suricata/ returned exit code 1 > make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/suricata_1.2.1-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
