Bug 243051 - yum confused about dependencies
yum confused about dependencies
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: James Antill
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-06 22:40 EDT by Michal Jaegermann
Modified: 2014-01-21 17:58 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-13 14:37:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2007-06-06 22:40:08 EDT
Description of problem:

A rawhide update from today brought libwnck-2.19.3.1-1.fc8.
yum did not protest about broken dependencies nor tried to
find some additional updates but 'package-cleanup --problems'
afterwards resulted in this:

Package compiz requires libwnck-1.so.21()(64bit)
Package gnome-applets requires libwnck-1.so.21()(64bit)
Package gnome-power-manager requires libwnck-1.so.21()(64bit)

with compiz-0.3.6-10.fc8, gnome-applets-2.18.0-9.fc8 and
gnome-power-manager-2.19.2-2.fc8 installed.  How come?

Version-Release number of selected component (if applicable):
yum-3.2.0-1.fc7
Comment 1 Michal Jaegermann 2007-06-07 20:00:15 EDT
After today updates complaints above were resolved; but
after a straight 'yum update' those were replaced by:

Package k3b requires libmpcdec.so.3()(64bit)

Indeed, a corresponding package was updated to
libmpcdec-1.2.6-2.fc8 and that one does not provide
libmpcdec.so.3.

It looks that yum really stopped paying attention to
dependencies, at least sometimes, and I have a gnawing suspicion
that this may be true for F7 as well.
Comment 2 Jeremy Katz 2007-06-07 20:17:28 EDT
Are you using --skip-broken or using something like the yum shell (or
pirut/yumex) and deselecting things after getting a failure?
Comment 3 Michal Jaegermann 2007-06-07 20:49:30 EDT
> Are you using --skip-broken ...

Nope!  As I said in comment #1 these were results of a straight
'yum update'.  No other options although 'yum-skip-broken' package
is indeed present on an installation.

BTW - it would be nice if one could rely, when needed, on
'skip-broken'.  This used to work in the past.

Oh, and when I looked closer k3b was even in the same set
of updates from today together with libmpcdec.
Comment 4 Panu Matilainen 2007-06-12 14:56:17 EDT
This sounds a whole lot what like I reported and Jeremy already fixed on
yum-devel: https://lists.dulug.duke.edu/pipermail/yum-devel/2007-June/003753.html
Comment 5 Michal Jaegermann 2007-06-12 16:21:27 EDT
There seems to be here some extra twist though.  The referenced message
from 'yum-devel' says:
> when a 
> package which is not part of the transaction set gets it's dependencies 
> broken by an update.

As noted in comment #3 both 'k3b' and 'libmpcdec' packages were parts
of the same transanction.  Still 'k3b' ended up with broken dependencies
(and, as for now, rawhide 'k3b' still is in that way). One can only hope
that the same fix is applicable.
Comment 6 Jeremy Katz 2007-06-13 14:37:13 EDT
Okay, this should be fixed up in yum cvs (I fixed another case where this can
occur).  yum 3.2.1 should be out shortly and will have the fix
Comment 7 Ralf Corsepius 2007-06-14 04:45:24 EDT
You guy might be interested in the thread starting at
https://www.redhat.com/archives/fedora-list/2007-June/msg03185.html

seems to me as if yum-3.2.0 is deep in limbo.

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