[100] in athena10
Re: Debathena materials not imported
daemon@ATHENA.MIT.EDU (ghudson@MIT.EDU)
Mon Mar 3 17:09:13 2008
Date: Mon, 3 Mar 2008 17:08:29 -0500 (EST)
From: ghudson@MIT.EDU
Message-Id: <200803032208.m23M8TX6024473@outgoing.mit.edu>
To: Tim Abbott <tabbott@mit.edu>
CC: Greg Hudson <ghudson@mit.edu>, athena10@mit.edu
In-reply-to: <Pine.LNX.4.64L.0801151329090.24714@vinegar-pot.mit.edu>
> - OpenAFS does not use the debathenificator framework because we do
> not actually change the Debian packaging of OpenAFS; we're only
> building it. The workflow involves 3 scripts:
I've imported a couple of missing support files and adapted these
scripts. I'm running into a couple of problems:
* find-openafs-kernels produces an empty list for dapper-amd64 and
dapper-i386. apt-file update is getting an empty Contents file.
I haven't looked into this very much except to note that it also
happens on debuild.mit.edu if I run the original Debathena script
in /mit/debathena/packages/third/openafs.
* The result of find-openafs-kernels includes a whole bunch of amd64
packages for sarge-i386, and one for lenny-i386. I don't know if
this is wrong or merely puzzling to me. I can handwave away the
amd64 packages for sarge-i386 because Sarge has no amd64 port, so
maybe it had amd64-specific kernels without a full amd64 suite.
The lenny-i386 one can't be handwaved.
* 40 of the builds failed: one on lenny (specifically, the amd64
package mentioned above), 21 on edgy, 3 on feisty, and 15 on
gutsy. I notice the debathena locker also lists some failures; I
don't know if some of them are expected or not. The one failure I
looked into (the amd64 headers package on lenny) appeared to be
running into an order-of-includes problem.
Any insights are appreciated; otherwise I'll plug away at these
further on my own.
