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

Re: Working copy on a network share

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-09-23 13:32:14 CEST

On Sep 23, 2005, at 13:14, Colin JN Breame wrote:

>> I think you're instead saying that your repository is BerkeleyDB-
>> based, and that it is on a local disk on the server, but that your
>> working copy is on a Samba share, and that this is not working. If
>> so, that should be unrelated to the storage engine used for the
>> repository.
> My working copy is BerkelyDB based and is stored on a samba share.


> I was wondering if this was happening with the fsfs backend.

Unless I'm greatly mistaken, BerkeleyDB only comes into play for
storing the repository. Working copies are always stored in the same
way, regardless of repository backend, and do not use BerkeleyDB.

BerkeleyDB and FSFS are the two available storage engines for the
repository on the server, but as I said, this has nothing to do with
how working copies of that repository are stored on the client. I
don't even think the Subversion client has any way of knowing what
storage engine a repository is using.

> Has anyone else had this problem? (i'm using v1.1.4).

I'd recommend you use the latest version of Subversion, which is 1.2.3.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 23 13:34:10 2005

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

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