Bug 249501 - yum complaining about nonexistent conflict
Summary: yum complaining about nonexistent conflict
Alias: None
Product: Fedora
Classification: Fedora
Component: yum   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-25 08:13 UTC by Jonathan Kamens
Modified: 2014-01-21 22:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-25 13:43:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jonathan Kamens 2007-07-25 08:13:40 UTC
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.

Comment 1 Jonathan Kamens 2007-07-25 08:19:34 UTC
Tried "yum upgrade" instead of "yum update"; it didn't help.

I have yum-3.2.2-1.fc8.

Comment 2 Jonathan Kamens 2007-07-25 08:22:44 UTC
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

Comment 3 Jonathan Kamens 2007-07-25 08:24:41 UTC
(I have rpm-

Comment 4 Panu Matilainen 2007-07-25 08:51:36 UTC
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)...

Comment 5 Jeremy Katz 2007-07-25 13:43:56 UTC
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

Note You need to log in before you can comment on or make changes to this bug.