kde packages and yum?

Michael Schwendt mschwendt at gmail.com
Wed Oct 6 09:13:04 UTC 2010


On Tue, 5 Oct 2010 18:28:24 -0700, Rob wrote:

> ---> Package mesa-libGL-devel.x86_64 0:7.9-0.7.fc15 set to be installed
> --> Processing Dependency: mesa-libGL = 7.9-0.7.fc15 for package:
> mesa-libGL-devel-7.9-0.7.fc15.x86_64
> --> Processing Dependency: pkgconfig(libdrm) >= 2.4.15 for package:
> mesa-libGL-devel-7.9-0.7.fc15.x86_64
> --> Processing Dependency: pkgconfig(xxf86vm) for package:
> mesa-libGL-devel-7.9-0.7.fc15.x86_64
> ---> Package mesa-libGLU-devel.x86_64 0:7.9-0.7.fc15 set to be installed
> --> Processing Dependency: mesa-libGLU = 7.9-0.7.fc15 for package:
> mesa-libGLU-devel-7.9-0.7.fc15.x86_64

> ---> Package mesa-libGL.i686 0:7.9-0.7.fc15 set to be installed
> --> Processing Dependency: mesa-dri-drivers(x86-32) = 7.9-0.7.fc15 for
> package: mesa-libGL-7.9-0.7.fc15.i686

So, that's the part where  mesa-libGL = 7.9-0.7.fc15  is required by
mesa-libGL-devel, and _any arch_ will suffice. Hence if the i686 build
of the pkg is the only one with version-release 7.9-0.7.fc15, that one
resolves the dependency.

As why that happens, you could have done a _little_ bit of homework.
It's not unreasonable to expect a user of Rawhide to be capable of
dealing with such problems. For example, if the installed mesa-libGL.x86_64
is newer than the mesa-libGL-devel.x86_64 in the repositories due to
switching mirrors temporarily, something like this can occur.

Query your local RPM database for all Mesa packages: rpm -qa mesa\*
Query the repositories for available Mesa packages: yum list mesa\*
What do you get?

Further, as Rawhide is updated almost daily, is your installation
up-to-date? Is the problem reproducible after a "yum -y update --skip-broken"?
Are you set up to use Rawhide (= F-15 development) only? Or do you also have
F-14 repositories enabled accidentally?

And a final request, please look into learning how to "Reply" to messages
posted to the list (in order to maintain threads of messages) instead of
composing entirely new ones. You've created three threads for your issue.


More information about the test mailing list