On Oct 24, 2008, at 02:44, Remigiusz Samborski wrote:
> We are using subversion in many website projects. Lately our
> servers where updated to use suExec
> PHP. suExec requires that php files have permissions 644 - no write
> permission for group or other.
>
> Svn client which is used to update and checkout websites keeps
> creating files with wrong
> permissions. We need to manually change back to proper permissions.
> For instance:
>
> # ls -l index.php
> -rw-r--r-- 1 perpedes perpedes 3060 Oct 23 18:34 index.php
> # rm index.php
> # umask
> 0022
> # svn update
> Restored 'index.php'
> At revision 18.
> # ls -l index.php
> -rw-rw-r-- 1 perpedes perpedes 3060 Oct 23 18:40 index.php
> ^ - the group write bit keeps getting set
>
> The problem occurs only when 'svn update' creates new files.
> Modified files keep proper permissions.
> We are using svn+ssh repository access method. I tried looking for
> answers, but without any luck.
Do you get the same behavior if you first check out a brand new
working copy?
How are the permissions of the pristine files in .svn/text-base/?
Version of Subversion? OS?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-25 00:00:00 CEST