On 4/17/06, Mark Slater <lists@humanesoftware.com> wrote:
> I'm working with two others on the ongoing maintenance of a live
> website (for a university course). We each make our changes in a
> local (private) working copy, and only run "svn update" on the copy
> on the server. The server is some recent-ish version of Solaris, and
> runs svn 1.2.3.
>
> We're having problems though, because the permissions in the .svn
> directories will frequently prevent anyone but the owner of the file
> from changing it. The versioned files themselves don't seem to have
> this problem as often. Our current solution is an update script that
> runs chgrp and chmod recursively on the site, first changing the
> group of all the files and then changing the permissions bits on all
> of them, but this seems less than optimal.
>
> I saw the bug report for Issue 1509, that seems to indicate sharing
> the working copy has been supported since svn 1.1. What might we be
> doing wrong? Has anyone come up with a more "proper" way of handling
> this situation?
Make sure your groups and umask are set correctly, and it should work
just fine. I do this all the time.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 18 00:46:31 2006