Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 37905 - vcron -> vixie-cron change leaves file in init.d and makes emerge complain about a service conflict
Summary: vcron -> vixie-cron change leaves file in init.d and makes emerge complain ab...
Status: RESOLVED DUPLICATE of bug 8423
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Gentoo Linux bug wranglers
URL: http://ars.userfriendly.org/cartoons/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-11 14:06 UTC by LionsPhil
Modified: 2005-07-17 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LionsPhil 2004-01-11 14:06:01 UTC
After an emerge -uv world, which updated vixie-cron, I was told to use rc-update to remove 'vcron' and add 'vixie-cron', which I did. However future emerges ended with a warning:

>>> Regenerating /etc/ld.so.cache...
 * Caching service dependencies...
 *  Service 'vcron' already provide 'cron'!;
 *  Not adding service 'vixie-cron'...                     [ ok ]
>>> (whatever I just emerged) merged.

It appears that, although 'rc-update show' and 'emerge -s vcron' indicated that vcron was gone, it still had a script in /etc/init.d/. Moving this (to a backup folder in ~) has caused the error to go away. It appears that either 'rc-update del' isn't removing it properly, or emerge is picking it up but shouldn't be.

(The system was completely up-to-date and etc-update had been run.)

See URL for an external comment board discussion of this bug.
Comment 1 SpanKY gentoo-dev 2004-01-11 14:17:12 UTC

*** This bug has been marked as a duplicate of 8423 ***