> > We're currently running six machines for m68k. One has the database > > locally, the others use ssh for wanna-build. I fail to see the problem > > here (other than getting enough people to process the logs, of course). > > Although my time is limited, I'm willing to do my share of this work if > someone fills me in.
Fine, I'll be happy to answer any questions that might arise. If you have access to the wanna-build CVS, get the stuff there. Otherwise, use the latest source at http://people.debian.org/~cts/wanna-build/ and build it on your PPC (just did that). Install sbuild and buildd and get sbuild going (edit /etc/sbuild.conf.local and ~/.sbuildrc). The next task would be setting up the chroot environment, I'd prefer to just copy the one Dan uses on voltaire for starters but he'd need to create a tar snapshot from that first. If there's a base.tgz for unstable we can create the chroot environment from there though. I've not found it in the package pool so if someone can point me to the proper place I'd appreciate that. I'm sorry if that seems like a lot of work to get started but I've never worked with chroot on PPC. I'll send you a short setup guide for chroot and buildd later to help in the further steps. > > Fine by me. I'm not keen on the job anyway. My build machine would be a > > Powerbook, and that means it's not going to be online all of the time. If > > there's someone else who would like to volunteer, I'd be happy to get you > > started on setting up the autobuilder. > > Unfortunately I don't have access to a 24/7 PPC machine so I'd be building on > this Pismo as well. That'll just have to do (better than a Lombard anyway). I've cleaned out 1.2 GB on an external SCSI disk, that should be enough. I'm a bit fuzzy on how to handle access to the build logs though. Michael
