Re: more trouble with 1.1 upgrade
In article [EMAIL PROTECTED] you write: 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. Uh, for bsdutils read debian-utils throughout. savelog was moved to debian-utils, not bsdutils. Austin (bsdutils maintainer)
Re: more trouble with 1.1 upgrade
Scott Barker writes (Re: more trouble with 1.1 upgrade): Ian Jackson said: Yes. cron needs to have savelog removed. 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. Ian.
Re: more trouble with 1.1 upgrade
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
Re: more trouble with 1.1 upgrade
Ian Jackson said: Yes. cron needs to have savelog removed. 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? Could be trouble... Also, I notice that at did not properly update /etc/crontab. I was left with the following entry: * * * * * rootatrun -d 0.5 Rather than what should have been added: * * * * * rootatrun -d -l 0.5 I'm not terribly familiar with perl, so I don't know why the at.postinst script didn't work. This has been fixed in the most recent at package, I believe. As of version 2.9a-11, it hasn't. The perl script seems to try and fix it, but didn't quite manage to do it on my system (which was 0.93R6). I believe the maintainer of the package is looking into it. -- 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) ] Management's biggest problem is all the unemployed people on the payroll. - From rec.humor
Re: more trouble with 1.1 upgrade
Scott Barker writes (more trouble with 1.1 upgrade): I got a message from dpkg when installing cron: dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/bin/savelog', which is also in package debian-utils Is it the same savelog? Yes. cron needs to have savelog removed. Also, I notice that at did not properly update /etc/crontab. I was left with the following entry: * * * * * rootatrun -d 0.5 Rather than what should have been added: * * * * * rootatrun -d -l 0.5 I'm not terribly familiar with perl, so I don't know why the at.postinst script didn't work. This has been fixed in the most recent at package, I believe. Ian.
Re: more trouble with 1.1 upgrade
On Sun, 19 May 1996, Scott Barker wrote: I got a message from dpkg when installing cron: dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/bin/savelog', which is also in package debian-utils savelog has moved to debian-utils so that it may be in a base system. (cron is not a base package). Unfortunately a new version of cron has not been released yet. I guess I'll usurp cron and release a new version with savelog missing so there won't be a problem. Guy
Re: more trouble with 1.1 upgrade
Hallo Scott! }Also, I notice that at did not properly update /etc/crontab. I was left with }the following entry: } }* ** * * rootatrun -d 0.5 } }Rather than what should have been added: } }* ** * * rootatrun -d -l 0.5 } }I'm not terribly familiar with perl, so I don't know why the at.postinst }script didn't work. Which version of at do you use? I have relaxed the postinst script, but as far as I can see it doesn't check the last component. I will investigate this tonight (hopefully). You should be hearing from me then. Regards, Joey -- / Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg / / Wer ist Germany.Net? http://home.pages.de/~joey/ / - Dauerwerbesender seiner Abbonenten.-- Lutz Donnerhacke /
