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

Re: MacOS X problems---Corrupt repository

From: Blair Zajac <blair_at_orcaware.com>
Date: 2003-08-01 18:56:38 CEST

kfogel@collab.net wrote:
>
> "Hamilton Link" <helink@sandia.gov> writes:
> > I don't suppose there are any other ways in which the INSTALL file for
> > svn is increasingly out of date? It specifically says (still) that
> > 4.0.14 is the Berkeley DB version to use. Since I certainly have never
> > been able to definitively say what is and isn't required to run svn,
> > do people on the dev team occasionally give a quick peek at the FAQ
> > and INSTALL, etc. files?
>
> Generally, 4.0.14 is still the recommended Berkeley, but on Mac OS/X
> 4.1.24 or higher is required -- 4.0.14 will not work.
>
> We'd like to recommend 4.1.x for Subversion in general, but
> experiments have shown that it's slower. The problem may be more with
> the way we use Berkeley than with Berkeley itself. I can't quantify
> this precisely only because I don't have the threads or issues handy
> right now. Some people use 4.1.x anyway; as far as I know, they don't
> have correctness issues.

To put this back on the radar screen, there has been a number of issues
with people using 4.1.25 on Linux/FreeBSD boxes that have had repositories
that end up being corrupted where the only way to recover is to restore
a backup copy.

I'm hoping svn.collab.net will be moved again to 4.1.25 at some point to
get the experts on it.

See

http://www.contactor.se/~dast/svn/archive-2003-04/0734.shtml

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 1 18:57:33 2003

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.