On Sat, Jan 23, 2010 at 12:17:18PM +0100, Philipp Kern wrote: > On Fri, Jan 22, 2010 at 10:43:16PM +0100, Kurt Roeckx wrote: > > Currently installing buildd is enough to try and start the daemon > > without even any configuration. This is not useful. (root gets > > mailed about it and things like that.) > > I guess it's debateable if it should be in a global crontab. However > it's indeed utterly useless to try to start an unconfigured buildd. > (Which it obviously doesn't seem to notice.)
Currently, we terminate if there are no distributions configured.
if (!...@{$self->get_conf('DISTRIBUTIONS')}) {
die "distribution list is empty, aborting.";
}
Is this what's getting mailed?
How would you prefer that we detect whether the daemon has been
configured?
> > Also, I do not want to run buildd-watcher, it's totaly useless
> > and annoying.
>
> That's your mileage that varies here, though.
We can add a configuration to not automatically run the
watcher if not all buildd admins want it. OTOH, consistency
between buildds is something IMO we should be aiming for.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
