Created attachment 322741 [details] Yum output for "yum update --skip-broken" Description of problem: yum update --skip-broken fails with the following error: > Running rpm_check_debug > ERROR with rpm_check_debug vs depsolve: > libdb-4.3.so()(64bit) is needed by (installed) cyrus-sasl-lib-2.1.22-18.fc10.x86_64 > libdb-4.6.so()(64bit) is needed by (installed) rapidsvn-0.9.6-3.fc10.x86_64 > Complete! > (1, [u'Please report this error in bugzilla']) Version-Release number of selected component (if applicable): yum.noarch 3.2.20-3.fc10 installed cyrus-sasl-lib.x86_64 2.1.22-18.fc10 installed cyrus-sasl-lib.i386 2.1.22-19.fc10 installed cyrus-sasl-lib.x86_64 2.1.22-19.fc10 installed rapidsvn.x86_64 0.9.6-3.fc10 installed compat-db.x86_64 4.6.21-4.fc10 installed (providing "libdb-4.3.so()(64bit)") compat-db.x86_64 4.6.21-5.fc10 rawhide (providing "libdb-4.6.so()(64bit)") compat-db46.x86_64 4.6.21-5.fc10 rawhide (providing "libdb-4.6.so()(64bit)") How reproducible: Have packages installed as per the attached. Perform "yum update --skip-broken" Actual results: The poor mite falls over. Expected results: Things proceed smoothly and I have an up-to-date system.
Created attachment 322742 [details] Output of "yum list all"
Please check this one https://bugzilla.redhat.com/show_bug.cgi?id=468785#c15
Replacing /usr/lib/python2.5/site-packages/yum/__init__.py as per https://bugzilla.redhat.com/show_bug.cgi?id=468785#c20 produces the output I'm about to attach, which seems to fix the issue. I imagine the transaction check error is now a packaging issue ;-). Thanks for your help!
Created attachment 323133 [details] Yum output for " yum update -d 7 --skip-broken -y"
i look like it solves part of the error, but introduces a new one by pulling in the i386 version of the already skipped compat-db45.x86_64. I have to dig a little deeper to fix this one.
Could you please replace /usr/lib/python2.5/site-packages/yum/__init__.py again and retest.
from here http://yum.baseurl.org/gitweb?p=yum.git;a=blob_plain;f=yum/__init__.py;hb=yum-3_2_X :)
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug seems to have disappeared at some point; I'm not quite sure where. For reference, my current yum version is now 3.2.20-4 (it was previously 3.2.20-3). I imagine given its new lack of reproducibility, this should now be closed? Many thanks for your help in trying to track it down (and I assume fixing it too).
yum-3.2.21-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/yum-3.2.21-2.fc10
yum-3.2.21-2.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/yum-3.2.21-2.fc9
yum-3.2.21-2.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing-newkey update yum'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-0460
yum-3.2.21-2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update yum'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-0562
yum-3.2.21-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
yum-3.2.21-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.