Michael Schmitz wrote:
On Wed, Jul 11, 2007 at 07:51:28PM +0200, Luk Claes wrote:
Luk Claes wrote:
Stephen R Marenka wrote:
On Thu, Jun 28, 2007 at 11:24:09AM +0200, Michael Schmitz wrote:
hostname: crest.debian.org aka crest.biophys.uni-duesseldorf.de
architecture: m68k
buildd admin(s): Adam Conrad <[EMAIL PROTECTED]>
local admin: Michael Schmitz <[EMAIL PROTECTED]>
I suppose this answers why crest never seems to be caught up on logs
these days. I dropped Adam an email a while back, but I never heard from
him. I suppose that means a4000t is gone for good too?
I think one of us needs to become primary on crest. Any volunteers? :)
Well, I'd love to help out with oldstable and oldstable-security, if that
would mean becoming primary, secondary or whatever on crest and taking care of
all suites, so be it. Though there might be better candidates?
Just to confirm that my offer to help out still stands. Please take care of
oldstable and oldstable-security or let me help.
I'm all for it. I'd rather not take on another buildd, atm. :)
What do you say Michael?
Seconded. I can't take more buildds, either. I'll try to sort out the
assignment of chroots to releases first, though.
For unstable crest is doing fine IMHO, though it's not used for
oldstable(-security) as it only builds packages for a suite when
needs-build > 10.
If I want to interact with wanna-build for m68k, am I supposed to use
crest's access to wanna-build or should I be added (centrally) to the
wb-m68k group? If the latter can someone that has already group
membership ask for my inclusion?
I noticed some things which could need some buildd maintainer action on
at least thing2, evolvotron, zeus, vivaldi and poseidon. All the
mentioned hosts have some packages in Uploaded for more than the usual
time. The trick is to remove the corresponding .upload files in their
upload directories to try to reupload the packages. If that still fails,
there is probably a more severe problem (might be a REJECT due to file
corruption or something similar).
It would also be a good idea to look at the Failed/Maybe-Failed packages
for packages that failed because of chroot problems
(linux-kernel-headers -> linux-libc-dev, ghc maintainer script mess) or
timeouts (after 15 minutes of no output) for the buildd you maintain.
Probably it would also be a good idea to revisit the packages in
Dep-Wait and Failed altogether...
If possible, please fix this problems (feel free to ask for more
information) or provide me access so I'm able to fix them.
Thanks.
Luk
PS: I'm currently not doing any porter work (for instance bootstrapping
toolchain packages or working to get the Coldfire fixes), though when I
could get access to the needed hardware and support (possibility to ask
for possibly dumb questions), I would consider to help...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
