Re: buildd failures for amd64?
Je 2006/07/20(4)/13:07, Goswin von Brederlow skribis:
> checking for ICMP ping syntax... Terminated
> make: *** [config.status] Error 1
> Build killed with signal 15 after 150 minutes of inactivity
Yes, I've seen it in the webpage. But it doesn't appear when I run
fakeroot debian/rules binary
manually. So either something strange is going on on the buildd amd64 machine,
or the package has an unreproducing bug.
> In the past we had a few packages just hang in sbuild during build for
> no concernable reasons. This might be a new one with the same
Yes. Although most packages are available for amd64, whenever I noticed
an unavailable package, I could manually build it without any changes.
So maybe it would be useful to send a STOP instead of TERM signal to the
process (and an email to the owner), go on with the next package, and
let the owner of the machine find out later what went wrong with the
build (connecting to the stopped process with gdb and friends).
(with a max number of STOPped builds of cource)
> To run a buildd you would also need to be a DD.
Well, I still get my email@example.com email:). Maybe I still am a DD?
> But you can do what you do now.
OK, that's what I'll do then.