Hi, 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.) Also, I do not want to run buildd-watcher, it's totaly useless and annoying. Kurt
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.) That's your mileage that varies here, though. Kind regards, Philipp Kern
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?
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
I have no idea, zobel would know, he got the mail. Maybe the presense of a .builddrc file? Kurt