Bug#267413: Running a debugging command on a buildd?
Dear Martin, dear James,
I'm contacting you as buildd admin's (I don't know Martin's exact role,
Laszlo 'GCS' Boszormenyi adviced me to contact you).
I'm trying to debug RC #267413, a FTBFS of zope assigned to tetex-bin,
and it seems that the problem is only triggered in some special
circumstances on a buildd: It is not reproducible in the unstable
chroots on merulo (ia64, one of the failing arches), a pbuilder
environment on i386, or an sbuild chroot I locally set up on i386.
But it reproducibly happens on the buildd's, on ia64, powerpc, hppa,
alpha, sparc, m86k, arm (but not on s390, i386 is not tried by a
buildd).
The actual error message is
ebiandoc2ps debian/doc/zope-policy.sgml
debiandoc2ps: ERROR: zope-policy.ps could not be generated properly
debiandoc2ps: rerun with the -v option to found out why
make: *** [zope-policy.ps] Error 1
And the only way to debug this seems to be to follow this advice: run
debiandoc2ps -v zope-policy.sgml.
I do not want to upload (NMU) the package just to introduce that switch,
and have all buildd's try it again, mostly in vain of course, just to
allow me to actually fix it. Is there any possibility that I get a
buildd of one of the failing arches just for trying to build a minimal
version of this zope package, that only contains this step? Or is there
any other way to execute such a command after installing the necessary
dependencies in a buildd environment?
Many thanks in advance, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Reply to: