What is your umask? Subversion may simply be setting your files to
your umask settings. You also may want to try using svn:// as a
protocol instead of file://. I never use file://, even if I am the
only one using the repository.
On Mon, Feb 23, 2009 at 1:46 PM, Kynn Jones <kynnjo_at_gmail.com> wrote:
> I have a sporadic problem with subversion that is driving me absolutely
> insane: committing a revision can cause the permissions of the underlying
> file to be changed.
> I cannot predict when such behavior will occur. Everything will be fine for
> several commits, and, one fine moment, even though I have not changed the
> permissions in the underlying file, the commit will cause these permissions
> to change. It looks like this:
> % ls -l path/to/some/file
> -rw-r--r-- 1 jones jones 7653 2009-02-20 21:39 path/to/some/file
> % svn ci -m '' /path/to/some/file
> Sending path/to/some/file
> Transmitting file data .
> Committed revision 1177.
> % ls -l path/to/some/file
> -rw------- 1 jones jones 7653 2009-02-23 13:38 path/to/some/file
>
> To make matters worse, even if I change the permissions back to what they
> were before the commit, every subsequent commit will change them back to the
> unwanted value. Grrrr!!!
> FWIW, at the moment I'm the only person making changes to these files
> (though other uses check them out for viewing the source code).
> Is there some way to tell subversion to leave the permissions alone??
> Is this insane behavior documented anywhere?
> This behavior is totally unpredictable (by me at least), so I cannot provide
> a reproducible example.
> TIA!
> Kynn
>
>
--
--
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1216257
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-23 21:18:46 CET