Re: buildd administration
On Fri, Dec 09, 2005 at 09:43:36AM +0100, Frank Küster wrote:
> Ingo Juergensmann <firstname.lastname@example.org> wrote:
> > On Thu, Dec 08, 2005 at 10:32:40PM +0100, Frank Küster wrote:
> >> > Feature requests and other things are always welcome! I can't know what you
> >> > want until you tell it to me. ;)
> >> Nothing - these the questions I was mainly interested in regarding
> >> buildd's:
> >> - is my package already built everywhere, so that it can go into
> >> testing?
> >> - did it FTBFS, and do the logs give indication why?
> >> - How can I get information from "inside" a buildd, e.g. temporary files
> >> created during a failed build.
> >> The first two can be answered without buildd.net (and actually I never
> >> was very much interested in "so when will it be built"?), the latter
> >> needs, well, a buildd admin must contact me...
> > A buildd admin doesn't see much more than what you can see in the build
> > logs. Basically the build logs is all a buildd admin see.
> But the buildd admin for sure has read access to /tmp in the build
> chroot? Assuming that /tmp isn't cleared after each build, but just
> every couple of hours/days/whatever.
Due to disk shoreage on a significant amount of buildd's, to the best of
my knowledge, the build tree is removed quite immediately after the
build finishes, and only a rebuild would be able to give you more info.
But surely, a porter owns the hardware in question too, and can simply
test-built it himself? *That* is work that any interested porter can do,
in the process, debugging the problem, and ultimately filing a useful
bugreport, hopefully with patch -- and maybe do a porter NMU later, even
-- prefereable still with i386 or so so that it is verified that this
time around, the buildd indeed is capable of building the package.
Yes, there can be hardware or software (kernel) differences between
the porter's machine and the buildd. If that is the case, indeed one
should contact the buildd administrator in question if more info is
needed, but generally, I'd expect porters to be able to know their
hardware well enough to find out what the issue is anyway.
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)