Bug#442691: ocamlodbc: FTBFS if build twice in a row
Package: ocamlodbc
Severity: important
Version: 2.15-1
User: debian-qa@lists.debian.org
Usertags: qa-doublebuild
Hi,
Lucas Nussbaum has rebuilt the whole archive on i386 and your package FTBFS if
built twice in a row with the following error:
dh_md5sums
dh_builddeb
dpkg-deb: building package `libocamlodbc-ocaml-dev' in `../libocamlodbc-ocaml-dev_2.15-1_i386.deb'.
dpkg-genchanges -mLucas Nussbaum <lucas@lucas-nussbaum.net>
dpkg-genchanges: including full source code in upload
dpkg-buildpackage: full upload (original source is included)
******************************************************************************
Build finished at 20070905-2301
#### END OF BUILD NO 1 ####
############
#### RUNNING BUILD NO 2 ####
############
dpkg-buildpackage: source package is ocamlodbc
dpkg-buildpackage: source version is 2.15-1
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 2.15-1
/usr/bin/fakeroot debian/rules clean
dpatch deapply-all
reverting patch makefiles from ./ ... ok.
rm -rf patch-stamp patch-stampT debian/patched
dh_testdir
dh_testroot
rm -f build-stamp
[ ! -f master.Makefile ] || /usr/bin/make clean_all
make[1]: Entering directory `/build/user/ocamlodbc-2.15'
make[1]: *** No rule to make target `clean_all'. Stop.
make[1]: Leaving directory `/build/user/ocamlodbc-2.15'
make: *** [clean] Error 2
******************************************************************************
Build finished at 20070905-2301
#### END OF BUILD NO 2 ####
FAILED [dpkg-buildpackage died]
The full build-log can be found at: http://people.debian.org/~lucas/logs/2007/doublebuild-09-05/failed-build-2/
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems. All
packages have been rebuilt twice in a row, with unpack, build, clean,
build.
Please read the mail of Martin Zobel-Helas on debian-devel [0], for a explanation
for this mass bug filling.
[0]: http://lists.debian.org/debian-devel/2007/05/msg00490.html
Reply to: