Re: yum update -> Missing Dependency for libdevmapper.so.1.02 (FC5)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 17/03/07, J.Moore wrote:
This is the first problem I've ever had with missing dependencies using
yum... Could someone point me in the right direction to find the
problem?

Thanks,
Jay

# yum update
Setting up Update Process
Setting up repositories

-snip-

---> Package cups.i386 1:1.2.8-1.fc5 set to be updated
---> Package evolution-data-server.i386 0:1.6.3-2.fc5 set to be updated
---> Package dhcdbd.i386 0:1.15-2.FC5 set to be updated
---> Package tcpdump.i386 14:3.9.4-4.fc5 set to be updated
---> Package cups-devel.i386 1:1.2.8-1.fc5 set to be updated
---> Package kernel-doc.noarch 0:2.6.20-1.2300.fc5 set to be updated
---> Package kernel.i686 0:2.6.20-1.2300.fc5 set to be installed
---> Package desktop-printing.i386 0:0.19-9.fc5 set to be updated
---> Package parted.i386 0:1.8.2-1.fc5 set to be updated
---> Package gnupg.i386 0:1.4.7-1 set to be updated
---> Package cups-libs.i386 1:1.2.8-1.fc5 set to be updated
---> Package pyparted.i386 0:1.8.5-1.fc5 set to be updated
---> Package nss.i386 0:3.11.5-0.5.1.fc5 set to be updated
---> Package libpcap.i386 14:0.9.4-4.fc5 set to be updated
--> Running transaction check
--> Processing Dependency: libdevmapper.so.1.02(Base) for package:
parted
--> Processing Dependency: libdevmapper.so.1.02 for package: parted
--> Finished Dependency Resolution
Error: Missing Dependency: libdevmapper.so.1.02(Base) is needed by
package parted
Error: Missing Dependency: libdevmapper.so.1.02 is needed by package
parted

Typically this means that none of your installed packages and none of
the packages in your enabled repositories provides the needed
'libdevmapper.so.1.02'. This can also happen if an already installed
package or any in the enabled repositories upgrades device-mapper to
an incompatible version, which does not include the needed component.

Run

  rpm --query --whatprovides  libdevmapper.so.1.02

to see if any installed package is sufficient. For example:

 $ rpm -q --whatprovides libdevmapper.so.1.02
 device-mapper-1.02.02-3.2
 $ rpm -q --whatprovides 'libdevmapper.so.1.02(Base)'
 device-mapper-1.02.02-3.2

If the query does not print the device-mapper package, run

 rpm --query device-mapper

to find out what version is installed. It must be a version compatible
with Fedora Core 5. If you have an incompatible one, get a good one
and downgrade it with "rpm -Uvh --oldpackage file.rpm", then continue
with your yum update.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux