On Sun, Apr 10, 2005 at 09:29:00AM -0500, Steve Greenland wrote: > On 10-Apr-05, 08:22 (CDT), Gerrit Pape <[EMAIL PROTECTED]> wrote: > > I'm not sure whether the conversion of /var/spool/cron/crontabs should > > be guarded by the dpkg-statoverride test, IMHO only the chgrp and chmod > > of /usr/bin/crontab should be done conditionally, I didn't change that > > in the patch below though. > > The theory behind putting all of the changes inside the > dpkg-statoverride test is that *if* the admin has changed the > permissions/ownership on /usr/bin/crontab, they must *also* have > adjusted permissions/ownership on the user crontabs, or the thing just > won't work (or, they aren't using/allowing user crontabs at all). In any > case, they've taken responsibility, and I don't want to touch it.
Yes, sounds reasonable. > Gerrit, I'm not going to upload with this patch until after sarge has > released, as I don't think this is the time to introduce something as > big as this (not that the cron patch is a big deal, but that the whole > bcron alternative is). If you disagree, and really want to push this > into sarge, then convince the release managers and get back to me. I'm with you, I'm not eager to get bcron into sarge. It's a very new upstream and Debian package that should get a lot more user testing through unstable. It's just that I currently have time to work on it, and it makes for fun than other things ;-). I think I'll introduce it into unstable after sarge is freezed completely. Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
