On 12/03/2011 04:47 PM, Tim Evans wrote:
RHEL 5.7, yum reporting:
yum -y update
Loaded plugins: rhnplugin, security
Skipping security plugin, no data
Setting up Update Process
Resolving Dependencies
Skipping security plugin, no data
--> Running transaction check
--> Processing Dependency: xen-libs = 3.0.3-132.el5 for package: xen
---> Package xen-libs.i386 0:3.0.3-132.el5_7.2 set to be updated
--> Finished Dependency Resolution
xen-3.0.3-132.el5.i386 from installed has depsolving problems
--> Missing Dependency: xen-libs = 3.0.3-132.el5 is needed by package
xen-3.0.3-132.el5.i386 (installed)
Error: Missing Dependency: xen-libs = 3.0.3-132.el5 is needed by package
xen-3.0.3-132.el5.i386 (installed)
Seems to be saying the package is a dependency for itself, or am I
reading this wrong?
Thanks.
Tim,
ugh. Not this. This is a "known" bug that likes to peak his head up
every now and then. A quick search has several reported bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=582101
https://bugzilla.redhat.com/show_bug.cgi?id=604428
https://bugzilla.redhat.com/show_bug.cgi?id=683639
https://bugzilla.redhat.com/show_bug.cgi?id=752500
<credit to James Antill>
The workaround all depends on what the "root problem" is. We hit this
with xen/xen-libs a lot because they are in different channels post
install, but come on the same media. But it's not just a xen/xen-libs
thing, basically there are a few problems:
1. xen-1 and xen-libs-2 (or xen-2 and xen-libs-1) are installed. Yum
doesn't look for/see existing problems but rpm does see them. So you
often get problems at upgrade time. Often this is due to rpm --nodeps usage.
2. Broken rpm DB. While a package is installed, which provides foo, the
rpm API calls look for it and can't see it. "rpm --rebuilddb" _should_
fix this.
3. Another random difference between how yum sees the world and how
rpm does is that yum says "do this" and rpm says "no". Thankfully, this
is very uncommon.
4. Having both xen/xen-libs installed from media (correctly), and then
"yum upgrade" doesn't work because you don't have the channel with the
xen upgrade in it. This will cause yum to fail (not rpm, but some
people think it's the same error). This will then have people use rpm
--nodeps to work around the problem and they will then hit #1 at some
later point.
If #2 doesn't work, then you would want to get a full yum list output
with repos, and pkgs with 'yum --showduplicates list xen xen-libs' and
look it over.
HTHs,
~rp
--
+-----------------------------[ ro...@redhat.com ]----+
| Robin Price II - RHCE,RHCDS,RHCVA |
| Technical Account Manager |
| Red Hat, Inc. |
| w: +1 (919) 754 4412 |
| c: +1 (252) 474 3525 |
| |
+---------[ Dissenters will inevitably abhor. ]-------+
_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list
