This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
First Last Prev Next    This bug is not in your last search results.
Bug 112817 - Subversion server resolving to wrong version of db4
Subversion server resolving to wrong version of db4
Status: CLOSED DUPLICATE of bug 112245
Product: Fedora
Classification: Fedora
Component: subversion (Show other bugs)
1
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2004-01-02 15:16 EST by Sean Cier
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 14:00:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Sean Cier 2004-01-02 15:16:12 EST 
Description of problem:
Subversion server reports "bad database version: compiled with 4.2.52,
running against 4.1.25"

Version-Release number of selected component (if applicable):
subversion-0.34.0-3, httpd-2.0.48-3

How reproducible:
Always

Steps to Reproduce:
1. Install latest rawhide, including subversion
2. Set up a repository via svnadmin
3. Configure mod_dav_svn via /etc/httpd/conf.d/subversion.conf
4. Set ServerNamein httpd.conf
5. /etc/init.d/httpd start
6. Hit subversion URL (in my case, http://localhost/svn/repos)

Actual Results:  Browser reports Error 500: bad database version:
compiled with 4.2.52, running against 4.1.25
Similar error in error_log


Additional info:
Comment 1 Joe Orton 2004-01-03 08:27:51 EST 
This is probably because httpd was still loading libdb-4.1; please
reopen this bug if the issue remains when using httpd-2.0.48-4.

*** This bug has been marked as a duplicate of 112245 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:00:32 EST 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.