Bugzilla Bug 106978

Subversion ebuilds using the apr ebuild instead of subversions own apr should
make sure that the subversion binary will not be linked against a previous db
version. See http://bugs.gentoo.org/show_bug.cgi?id=98688#c2 for more details.
This problem happened to me while upgrading from subversion 1.2.3 to 1.2.3-r1,
because I generally dont update world --deep, which led to db-4.1 being the
latest installed version and subversion-1.2.3 being linked against it. During
the latest update apr and thus subversion have been linked against db-4.0
causing my repositories being inaccessible causing me one or two heart attacks
and a medium headache.

Reproducible: Always
Steps to Reproduce:
1.emerge subversion without >=db-4.2 installed and >=db-4.2 masked and
>subversion-1.2.3 masked
2.create a svn repository
3.remove the masks on subversion and db
4.remerge subversion with db-4.0 installed
5.try "svn ls" on the repository

Actual Results:  
svn ls failed with an error message similar to this one:

svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///path/to/rep'
svn: Berkeley DB error for filesystem /path/to/rep/db while opening environment:
DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: region error detected; run recovery

the suggested "svnadmin recover" would fail with an error message similar to
this one:

Repository lock acquired.
Please wait; recovering the repository may take some time...
*** glibc detected *** free(): invalid pointer: 0x08068250 ***
Aborted


Expected Results:  
The software should have succeeded :)

the 1.2.3-r1 version uses the db version that apr was installed with. I'll
think
about doing some checks on db versions. db probably needs this kinds of checks.

*** This bug has been marked as a duplicate of 98688 ***