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

RE: file:/// protocol based svn repository questions

From: Jeff Marver <jmarver_at_serlio.com>
Date: Thu, 18 Mar 2010 08:29:11 -0500

Hi Andy,

Thanks for the info!


Jeff Marver | Serlio Software Development Corporation | 414-771-1452 x224
Easily create great Use Cases and Requirements - www.casecomplete.com

-----Original Message-----
From: Andy Levy [mailto:andy.levy_at_gmail.com]
Sent: Wednesday, March 17, 2010 10:47 AM
To: Jeff Marver
Cc: users_at_subversion.apache.org
Subject: Re: file:/// protocol based svn repository questions

On Wed, Mar 17, 2010 at 11:30, Jeff Marver <jmarver_at_serlio.com> wrote:
> Hi all,
> We're using SharpSVN.SvnRepositoryClient.CreateRepository to create file:///
> protocol based svn repositories on shared Windows network drives. Can anyone
> tell me the exact permissions a Windows user will need to fully interact
> with the repository? We're recently run into a user that was able to lock a
> file but couldn't do a commit, the error indicated that the commit failed
> and a .tmp file couldn't be moved since it already existed in txn-current?
> The customer indicated that they had read and write access??

Full control.

> Also, I've seen quite a few posts on the Internet suggesting that sharing a
> file:/// protocol based svn repository is not recommended for multiple users
> and even discouraged. Can anyone confirm or refute this information?

Very bad idea. When you do this, anyone can corrupt or even delete the
whole repository with one errant keystroke. And you have no path-based
authorization. If someone uses a newer client with the repository,
older ones may not be able to read it. There /may/ be concurrency
concerns as well, but I'm not 100% sure on that.

Have a look at the final bullet point on

Set up a proper SVN server, you'll be much better off.
Received on 2010-03-18 14:29:06 CET

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