Re: File permission after update

Giulio Troccoli wrote:
> We use Subversion 1.4.4 on a Linux box with Apache. The user/group that
> runs apache is svn/svn, and umask for user svn is 000. We use a common
> WC to perform automatic merges. This WC is created once and then updated
> after every commit (in the post-commit hook)
>
> When I checked out the WC everything was fine: all files have rw
> permission for everybody and all directories have rwx permission for
> everybody.
>
> When I do an update however, and I have new directories, these are added
> with rwx permission for svn user only, and r permission for the group
> and everybody else. This is particularly true for the .svn directories
> too.
>
> The problem we're having is that when a user then tries to merge his
> changes, the script they use makes use of the WC and then commits from
> there. However Subversion complains that it cannot access a ./lock file
> and the commit fails.
>
> I'm sorry I cannot provide a more precise explanation, but we had to fix
> the problem straight away (which means a simple chmod) to allow the
> process to go through. Next time it happens I will make an effort and
> get more info.
>
> In the meantime, does anybody have any idea why this would happen? Has
> anybody experience something like this or similar?

Subversion isn't designed to have a shared working copy. The best fix
is to have a working copy for each user which will permit concurrent
work. The particular problem you are having is most likely being caused
by new files taking the primary group of the logged in user and
permissions based on his umask. You can fix that, but it's not the
right fix for this situation.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org