Description of problem: quick fix for user - manual perl-BerkeleyDB recomplication Version-Release number of selected component (if applicable): perl-BerkeleyDB-0.41-1.fc13.src.rpm How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I'd suggest hard-coding the BDB version as a dependency in perl-BerkeleyDB so that this shows up more quickly if db4 is rebuilt in future. The following works for me: # Need to know the exact DB version we're built against %global db_ver %(sed '/DB_VERSION_STRING/!d;s/.*Berkeley DB[[:space:]]*\\([^:]*\\):.*/\\1/' /usr/include/db4/db.h 2>/dev/null || echo 4.0.0) # Hard-code Berkeley DB requirement to avoid problems like #592209 Requires: db4 = %{db_ver} I can add this and push an update if you're busy at the moment Steve; let me know.
A rebuild of perl_BerkelyDB under mock fixed this. It stopped amavisd-new from working.
Which versions of the db4-devel and perl-BerkeleyDB packages do you have? I can reproduce this on Rawhide but not F-13 at the moment.
OK, I've reproduced it on F-13 now; will build an update shortly.
perl-BerkeleyDB-0.41-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/perl-BerkeleyDB-0.41-2.fc13
*** Bug 595831 has been marked as a duplicate of this bug. ***
*** Bug 595834 has been marked as a duplicate of this bug. ***
perl-BerkeleyDB-0.41-2.fc13 has been pushed to the Fedora 13 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 perl-BerkeleyDB'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/perl-BerkeleyDB-0.41-2.fc13
perl-BerkeleyDB-0.41-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.