Ian Jackson said: > Scott Barker writes ("Re: more trouble with 1.1 upgrade"): > > ok. So what happens when I install the new cron, and /usr/bin/savelog isn't > > in > > it? Won't dpkg remove it, since /usr/bin/savelog has been removed from > > /var/lib/dpkg/info/base.list? > > Err, bugger. I knew this --force-replaces thing was a bad idea. > > If you do this you'll have to reinstall bsdutils, but there's nothing > really that can be done about it. > > cron needs to be fixed.
That's what I thought. Just thought I'd mention the problem. Perhaps when cron is fixed, the bsdutils package should be bumped up a version, so that dselect will automagically re-install it. Or maybe the cron postinst script should spit out a message letting the user know that bsdutils should be updated. -- Scott Barker Linux Consultant [EMAIL PROTECTED] http://www.cuug.ab.ca:8001/~barkers/ (under construction) [ I try to reply to all e-mail within 5 days. If you don't ] [ get a response by then, I probably didn't get your e-mail ] [ (we have a sometimes sporadic connection to the internet) ] "Though we travel the world over to find the beautiful, we must carry it with us or we find it not." - Ralph Waldo Emerson