Re: daily pestering about s390 and sparc buildd failure
Ingo Juergensmann <ij@2004.bluespice.org> writes:
> Write DSA or the buildd admin to get your build-deps installed in dchroot.
This does not solve the problem.
> I see no problem with getting an account on some random sparc machine. For
> s390 this is different, but then again you can login on raptor and/or trex
> and request that your builddeps get installed.
It is as if you didn't bother to read and understand the problem
before you offer your advice. The problem is *specifically* that
sbuild (or something in its environment) seems to be broken. In the
absence of someone providing *root* in the build environment, so that
I can run apt-get myself and monitor what's going on--or someone with
root volunteering to debug the problem--I realized that a probe into
the buildd environment is the only workable solution.
The problem is that sbuild is failing to automatically install the
correct dependencies for packages which it is installing. Please read
the debian-devel posts in question before commenting further.
If you had read the previous messages on this topic on debian-devel,
you would know that your advice is not helpful.
If you want to help, that would be appreciated. But telling me not to
use the only actual mechanism for getting at the actual bug is not
useful.
Thomas
Reply to: