Red Hat Bugzilla – Bug 249501
yum complaining about nonexistent conflict
Last modified: 2014-01-21 17:59:01 EST
When I try to do "yum update" against the development repo, I get this during
the update transaction:
ERROR with rpm_check_debug vs depsolve:
Package vixie-cron conflicts with sysklogd < 1.4.1.
and then the transaction aborts there, i.e., no update actually happens.
Note that I have rsyslog-1.17.1-1.fc8 installed and do *not* have sysklogd
Note also that it does not appear that yum is actually trying to update vixie-cron.
There is no sysklogd installed, so there is no conflict between vixie-cron and
sysklogd < 1.4.1.
Tried "yum upgrade" instead of "yum update"; it didn't help.
I have yum-3.2.2-1.fc8.
This apparently isn't a yum-only problem. When I try to use "rpm -Fvh" on all
the RPMs downloaded by yum, I get, "sysklogd < 1.4.1 conflicts with
(I have rpm-18.104.22.168-0.6.rc3.)
My guess is that sysklogd gets pulled into the transaction set through the
vixie-cron dependency on virtual "syslog" provide or something like that. Please
check yum output carefully (or attach the full output of the update attempt)...
rsyslog in rawhide yesterday has a bogus provides that's causing this; it's been
fixed and built, but rawhide today died during the compose