Re: Checking buildd logs
On Sun, Nov 04, 2001 at 05:17:57PM -0800, Rick Younie wrote:
> Daniel Jacobowitz wrote:
> > On Sun, Nov 04, 2001 at 02:55:36PM -0800, Rick Younie wrote:
> > > Several developer machines run buildds if you want to check things
> > > out. gluck and voltaire for example.
> > If you look on voltaire, you'll notice that I take the lazy man's
> > approach to build daemons. It runs in a chroot, but it is by no means
> > empty; in fact, almost every time I find a missing build dependency, I
> > just toss the package in.
> It doesn't really matter because you don't file bugs :-)
> ...not a dig. There are several of us handling the m68k logs but
> it can still eat up a fair chunk of my computer time sometimes.
> I have no idea how one guy can do all the logs for an arch (or
> several arches) and still have a life.
Exactly. I don't file bugs, because in my experience enough bugs do
get filed, and I'm more interested in propogating the distribution
without losing my soul to it. I do a very cursory job - I describe
fails rather than investigating them, usually, and hope that someone
else will fix them. Usually, someone does :)
> Now that all the logs are centrally located at buildd.d.o has any
> thought been given to having volunteers file build failure bugs
> I'm wondering? Some problems are arch-specific but many aren't.
> Maybe Cc some repository when someone takes responsibility for a
> bug? Or would this be more hassle than it's worth?
Well, volunteers out on debian-powerpc have been doing this lately, and
it seems to work out well.
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer