Description of problem: Every DAV access to a svn repo stored in bdb backend fails: svn checkout http://127.0.0.1/repo svn: PROPFIND request failed on '/svn-001/repos' svn: Could not open the requested SVN filesystem From /var/log/httpd/error_log [Fri Jan 15 09:59:31 2010] [error] [client 127.0.0.1] (20014)Internal error: Berkeley DB error for filesystem '/var/www/svn-001/repos/db' while opening environment:\n [Fri Jan 15 09:59:31 2010] [error] [client 127.0.0.1] Could not fetch resource information. [500, #0] [Fri Jan 15 09:59:31 2010] [error] [client 127.0.0.1] Could not open the requested SVN filesystem [500, #160029] [Fri Jan 15 09:59:31 2010] [error] [client 127.0.0.1] Could not open the requested SVN filesystem [500, #160029] Version-Release number of selected component (if applicable): subversion-1.4.2-4.el5_3.1.ppc httpd-2.2.3-31.el5_4.2.ppc db4-4.3.29-10.el5.ppc Additional info: ppc only
The test case wasn't setting the file context.
Reopening. subversion.ppc64 is causing this bug - with this package installed svn can't access repository via mod_dav_svn (messages from comment#1 are logged). Simple removal of subversion.ppc64 afaik won't do - subversion package contains libraries too and those should be available in both ppc and ppc64 architectures.
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.6 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release.
The correct technical fix for this problem is to stop shipping the subversion package as "multilib"; i.e. only ship subversion.ppc, and drop subversion.ppc64 (or vice versa). This would cause upgrade issues, however, for any users already using (only) the arch variant which is dropped. For any users seeing this issue, the fix is to ensure that the only subversion package present on the system matches the arch of the mod_dav_svn package. (for example, "yum erase subversion.ppc64" should be sufficient) In a future release of RHEL (and in current Fedora releases), the subversion package will not be shipped for both arches any more, to avoid this problem.