found 592097 2.2.0-1 thanks On Sat, Aug 07, 2010 at 05:07:53PM +0100, Alastair McKinstry wrote: > >Hi, > > > >checking build dependencies is really so hard you always end up uploading > >broken packages?! > >| autoreconf: running: aclocal --output=aclocal.m4t > >| Can't exec "aclocal": No such file or directory at > >/usr/share/autoconf/Autom4te/FileUtils.pm line 326. > >| autoreconf: failed to run aclocal: No such file or directory > > > >Seriously… > > > > > Aargh. "Apt-get install autoconf" pulls in automake as a dependency > in my chroot, but > not build machines, for some reason. > This was a clean sid chroot, with build-essential + > build-dependencies + autoconf. > > Adding it explicitly.
Do you seriously think that you could skip proper testing that everyone else does? Imposing work on the buildd maints to get you to do proper work? autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --output=aclocal.m4t Can't exec "aclocal": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 326. autoreconf: failed to run aclocal: No such file or directory make[1]: *** [override_dh_auto_configure] Error 1 make[1]: Leaving directory `/build/buildd-cmor_2.2.0-1-powerpc-GhGv1f/cmor-2.2.0' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 cmor 2.2.0-1 is failing exactly the same. Which means that you didn't do proper build testing with either pbuilder or sbuild. There's a point to them, e.g. they don't install recommends, just like the buildds. Oh well. Regards, Philipp Kern
signature.asc
Description: Digital signature
