See below Reproducible: Always Steps to Reproduce: 1. Have an old vcron ebuild installed, and vcron added using rc-update 2. Emerge vixie-cron 3. Get this error message: * Caching service dependencies... * Service 'vcron' already provide 'cron'!; * Not adding service 'vixie-cron'... [ ok ] 4. Fine, whatever. Now do: "rc-update del vcron default" "rc-update add vixie-cron default". 5. I still the above error all the time. It's really annoying, and I've had this happen with other ebuilds before, like klogd and syslog-ng for example...
see thic link: http://forums.gentoo.org/viewtopic.php?t=121455
Ok, but a long-term solution still needs to be worked out for this. Users shouldn't have to delete what they have in /etc/init.d
I read somewhere that emerge will NEVER remove anything inside /etc. If an update need to remove/change something in there, it will prompt you to do so. And the "annoying" thing you just experience won't happen that often. I only saw a couple when developer rename/reorganize packages.
No, this also happened to me when I did a "routine" switch from syslog-ng to sysklogd (or whatever it's called). If Gentoo's policy is to not delete anything from /etc/ that is great. I prefer that. What is needed then, is a change to etc-update (to remove a file "interactively" which deemed unecessary, such as /etc/inti.d/vcron), or change the depscan.sh so it isn't so retarded.
there's also a bug about having like etc-update clean out unused files in CONFIG_PROTECT *** This bug has been marked as a duplicate of 8423 ***
