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

Re: Problems with permissions (changed vith svn commit)

From: Sebastijan V <sv7874_at_gmail.com>
Date: Sun, 07 Apr 2013 23:02:19 +0200

Sorry for late answer.

chmod prevents changing group and others permission.

I'm planning to use svn for /etc/ backup.
Is there any way to tell svn to leave premissions as they are?

Is umask 777 only option?

best regards, sebastijan
On 21.3.2013 14:23, Daniel Shahaf wrote:
> Try
> # umask 077
> (in the same shell, prior to testing)
>
> Sebastijan V wrote on Thu, Mar 21, 2013 at 02:50:52 +0100:
>> Hello
>>
>> I'm using Fedora. Until subversion-1.6.18-1 everything was OK.
>> From version 1.7.8-1 I have following problem:
>>
>> # touch testfile
>> # ls -la testfile
>> -rw-r--r--. 1 root root 0 Mar 21 02:49 testfile
>>
>> # chmod 600 testfile
>> # svn add testfile
>> # ls -la testfile
>> -rw-------. 1 root root 0 Mar 21 02:49 testfile
>>
>> # svn -m '' ci
>> # ls -la testfile
>> -rw-r--r--. 1 root root 0 Mar 21 02:49 testfile
>>
>> I don't think, that's OK.
>> I was searching on the net, how to preserve permissions, but didn't find
>> anything.
>> Is any option, to leave permissions as they are while svn commit?
>>
>> with */strace svn -m '' ci/* I can see 'chmod 644'
>>
>> best regards, sebastijan
Received on 2013-04-07 23:03:06 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.