Re: buildd failures for amd64?
Kurt Roeckx wrote:
On Thu, Jul 20, 2006 at 01:53:54PM +0200, Joost Witteveen wrote:
Yes. Although most packages are available for amd64, whenever I noticed
an unavailable package, I could manually build it without any changes.
Can you give me any list of packages that we should build, are
unavailable, and don't have an RC bug open that it failed to
Not anymore. I remember a that a few weeks (months?) ago apt-get-ing
from testing complained about a lot missing packages. But now at least
that works OK again for me. The other (other than nagios-plugins)
packages I remember compiling when they were unavailable for some time
in unstable were sendmail (after a security bug), and ntp
4.2.0a+stable-8.2. But both now are available from the testing archive,
so both problems have already been noticed.
In this case, it's a bug in the package where it
should actually specifiy a correct versioned build dependency.
Even though we could build it at a later time, we don't, and
expect the maintainer to upload a new version with that bug
BTW, are you sure it was builddeps in this case? the build haning in trying to ping localhost seems not to relate to builddeps.
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).
I don't see the point of this. It's probably reproducible in