Red Hat Bugzilla – Bug 830635
Package update fails due to a dependency problem
Last modified: 2014-06-10 19:28:20 EDT
Description of problem:
13:56:49 : ERROR: Error in yum Transaction : [u'ERROR with transaction check vs depsolve:', '/usr/bin/db_stat is needed by (installed) rpm-188.8.131.52-7.fc17.x86_64', u'Please report this error at https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=yum']
Version-Release number of selected component (if applicable):
Steps to Reproduce:
13:34:19 : ERROR: Error in yum Transaction : [u'ERROR with transaction check vs depsolve:', '/usr/bin/db_stat is needed by (installed) rpm-184.108.40.206-7.fc17.x86_64', u'Please report this error at https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=yum']
How to fix this? I get this when updating db4-util package. But another report says that this has been replace by db4_*. But I am unable to remove this package or find any relevant db4_* package under yum.
I had the same problem after having upgraded from F16 to F17.
I could solve the issue by doing (as root):
#yum clean all
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Usually when a message like this occurs it means one of the two things. Either the operation you request breaks some dependencies or the dependencies are already broken on your system for some reason.
The way to fix this is to manually fix the dependencies. You can do that either by erasing packages with broken deps or by installing packages that contain dependencies that are broken.
If something like this happens during an update, it's usually a problem of the package in question. If it happens during distro upgrade (F19 to F20 for instance), the experience says fedup is usually at fault.
In any case this is very likely not bug but there is no way near enough information here to know for sure what's happened. Closing ...
Or the Fedora updates in question weren't properly tested before being released.