On 17/11/2007, Timothy Murphy wrote: > > When I yum install kdebase-devel, > I am told that I require a whole lot of library files, > all of which are in fact already installed. > > I'm trying to work out how and why this occurs. > > -------------------------------- > [tim@elizabeth ~]$ sudo yum install kdebase-devel > ... > --> Running transaction check > ---> Package kdebase-devel.i386 6:3.5.8-3.fc7 set to be updated I assume that kde 3.5.8-3.fc7 is latest. But since you deleted some of the output, what does "yum repolist" show? > --> Processing Dependency: libkonq.so.4 for package: kdebase-devel > ... > --> Finished Dependency Resolution > Error: Missing Dependency: libkonq.so.4 is needed by package kdebase-devel > ... > [tim@elizabeth ~]$ locate libkonq.so > /usr/lib/libkonq.so > /usr/lib/libkonq.so.4 > /usr/lib/libkonq.so.4.2.0 First, it's a mistake here to use "locate". It does not matter what files are installed on your local disk. All that matters is what files will _still_ (!) be tracked in the RPM database after installing the new packages. Update packages can move/remove files. Especially when dealing with online repositories, use tools like "yum whatprovides ..." or "repoquery --whatprovides ...". Verify that nothing in the yum transaction tries to replace kdebase-3.5.8-3.fc7and the library SONAMEs provided by that package. > [tim@elizabeth ~]$ rpm -qf /usr/lib/libkonq.so.4 > kdebase-3.5.8-3.fc7 Second, yum complains about libkonq.so.4 not /usr/lib/libkonq.so.4 (two different albeit related things), so you would need to "rpm -q --whatprovides libkonq.so.4" or preferable "yum whatprovides libkonq.so.4".
