[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn upgrade -> db unusable

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-04-09 15:48:45 CEST

Sander Smeenk <ssmeenk@freshdot.net> writes:

> Hi,
> There's a lot about SVN that I really like, but there's one thing that I
> dislike. Each time I upgrade my SVN, my old repositories become
> unusable:

Subversion is still in development and has not yet released the first
stable version. See http://subversion.tigris.org/project_faq.html#stable

"Is Subversion stable enough for me to use for my own projects?
 Yes and No.

 We say "Yes" becasue [snip]

 We say "No" because there's a good chance that the filesystem might
 change before we go 1.0, and we don't plan on writing and testing and
 shipping conversion utilities."

> | Could not open the SVN filesystem at /var/svn/pj/ [500, #21048]
> | (2)No such file or directory: bad database version: 3.2.9 [500, #21048]

This indicates that you have a BerkelyDB version mismatch. Have you
managed to link mod_dav_svn against db-3.2.9 (I don't think this is
possible)? More likely, do you have apache linked against db-3.2.9?
Subversion requires you to use db-4.0.14, see section 6 in INSTALL.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 9 15:49:34 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.