Source: libiptcdata Version: 1.0.4-2 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»/build-python2.6' > 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»/build-python2.6' > make[2]: Leaving directory `/«PKGBUILDDIR»/build-python2.6' > make[1]: Leaving directory `/«PKGBUILDDIR»/build-python2.6' > touch install-stamp-python2.6 > dh_installdocs -plibiptcdata0-dev ./README ./NEWS ./TODO ./AUTHORS > dh_installexamples -plibiptcdata0-dev > dh_installman -plibiptcdata0-dev > dh_installinfo -plibiptcdata0-dev > dh_installmenu -plibiptcdata0-dev > dh_installcron -plibiptcdata0-dev > dh_installinit -plibiptcdata0-dev > dh_installdebconf -plibiptcdata0-dev > dh_installemacsen -plibiptcdata0-dev > dh_installcatalogs -plibiptcdata0-dev > dh_installpam -plibiptcdata0-dev > dh_installlogrotate -plibiptcdata0-dev > dh_installlogcheck -plibiptcdata0-dev > dh_installchangelogs -plibiptcdata0-dev ./ChangeLog > dh_installudev -plibiptcdata0-dev > dh_lintian -plibiptcdata0-dev > dh_bugfiles -plibiptcdata0-dev > dh_install -plibiptcdata0-dev --sourcedir=/«PKGBUILDDIR»/debian/tmp > dh_link -plibiptcdata0-dev > dh_buildinfo -plibiptcdata0-dev > dh_installmime -plibiptcdata0-dev > dh_installgsettings -plibiptcdata0-dev > dh_installdocs -plibiptcdata0-dbg ./README ./NEWS ./TODO ./AUTHORS > dh_installexamples -plibiptcdata0-dbg > dh_installman -plibiptcdata0-dbg > dh_installinfo -plibiptcdata0-dbg > dh_installmenu -plibiptcdata0-dbg > dh_installcron -plibiptcdata0-dbg > dh_installinit -plibiptcdata0-dbg > dh_installdebconf -plibiptcdata0-dbg > dh_installemacsen -plibiptcdata0-dbg > dh_installcatalogs -plibiptcdata0-dbg > dh_installpam -plibiptcdata0-dbg > dh_installlogrotate -plibiptcdata0-dbg > dh_installlogcheck -plibiptcdata0-dbg > dh_installchangelogs -plibiptcdata0-dbg ./ChangeLog > dh_installudev -plibiptcdata0-dbg > dh_lintian -plibiptcdata0-dbg > dh_bugfiles -plibiptcdata0-dbg > dh_install -plibiptcdata0-dbg --sourcedir=/«PKGBUILDDIR»/debian/tmp > dh_link -plibiptcdata0-dbg > dh_buildinfo -plibiptcdata0-dbg > dh_installmime -plibiptcdata0-dbg > dh_installgsettings -plibiptcdata0-dbg > dh_installdocs -plibiptcdata-bin ./README ./NEWS ./TODO ./AUTHORS > dh_installexamples -plibiptcdata-bin > dh_installman -plibiptcdata-bin debian/xml-man/en/iptc.1 > debian/xml-man/en/iptc.1: No such file or directory at /usr/bin/dh_installman > line 127. > make: *** [binary-install/libiptcdata-bin] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/libiptcdata_1.0.4-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 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-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
