Re: buildd failures for amd64?
Joost Witteveen <joost@iliana.nl> writes:
> Hi,
>
> I from time-to-time notice that amd64 doesn't have a package in
> unstable/testing, while most (all) other archs do. At the moment
> for example natios-plugins is compiled for most archs, but the amd64
> arch reports "maybe-failed":
>
> http://buildd.debian.org/fetch.php?&pkg=nagios-plugins&ver=1.4.3.0cvs.20060707-2&arch=amd64&stamp=1152532502&file=log&as=raw
> http://buildd.debian.org/build.php?arch=&pkg=nagios-plugins
>
> When trying myself
> apt-get source nagios-plugins; cd n*; fakeroot ./debian/rules binary
> on my amd64 box, I get the proper nagios-plugins*.deb's in 136 seconds,
> so it looks like there was something wrong with the build box for amd64.
>
> So, I wonder, could my box help with the compiling (I have hd and bandwidth
> to burn)? (If so, does anyone know where to apply?)
>
>
> Thanks!
>
> (I used to be a debian developer, joostje@debian.org)
The problem is this:
checking for ICMP ping syntax... Terminated
make: *** [config.status] Error 1
Build killed with signal 15 after 150 minutes of inactivity
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
effect. Someone has to babysit the buildd while a new try is made to
check what actualy is going wrong.
As you can seen on
http://unstable.buildd.net/buildd/amd64_stats.png
there is no backlog of package to build (Neews-Build line) and the
buildds are idle most of the time. To run a buildd you would also need
to be a DD. But you can do what you do now. Look for failed packages,
see why they failed and write patches where possible. You just can't
do much on failures caused by the buildd (software).
MfG
Goswin
Reply to: