Description of problem: The last real update (other than automatic rebuilds and dist-git conversion) of sysklogd was in January 2009. Furthermore, it causes serious breakage if used in F16. The maintainer has agreed to EOL it. To make sure it does not remain installed, it should be properly Obsoleted by rsyslog. From today's #fedora-devel chat: <michich> kanarip, hello. did you see bug 744523 and bug 714778? What do you think about removing sysklogd from Fedora? <BlackFox> .bug 744523 <zodbot> BlackFox: Bug 744523 no network after boot - https://bugzilla.redhat.com/show_bug.cgi?id=744523 <BlackFox> .bug 714778 <zodbot> BlackFox: Bug 714778 cronie messages end up in /var/log/messages where they do not belong - https://bugzilla.redhat.com/show_bug.cgi?id=714778 <kanarip> michich, i'm most definitely not going to be able to modify sysklogd in this way, and with EL 6 i have no need for sysklogd being in Fedora either <michich> kanarip, OK, will you do the EOL process? <michich> kanarip, should I ask rsyslog to add Obsoletes for sysklogd? <kanarip> sure, though i'm not sure how the EOL process works i'll have a look later this week <michich> kanarip, https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life <kanarip> i suppose rsyslog would need to obsolete sysklogd indeed <kanarip> michich, i'm strapped for time at the moment, i'll have a look at EOL for sysklogd later this week <michich> kanarip, thanks
I see you added it in rsyslog-5.8.6-1: Obsoletes: sysklogd Unversioned obsoletes are generally considered bad. Should the package be resurrected in the future, the unversioned obsoletes rule would prevent it. The last built version is sysklogd-1.5-10.fc15, so please use: Obsoletes: sysklogd < 1.5-11 as per http://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages