I have set up my tortoise svn config file so that all files within my
repos are set up with the property * = svn:needs-lock. This worked
perfectly until recently my working copy, which is stored on a network
sharedrive, no longer made files read only. The grey overlay icon is
still shown for all files, but when I look in the properties of the
files the access is -rw-r--r-- when they should be -r--r--r--. I can
even change the permissions of the files manually to -r--r--r-- and
then when the lock is gathered the permission change as expected to -
rw-r--r--, but when I release the lock the permissions stay as -rw-r--
r-- when they should be -r--r--r--.
I have checkout a working copy to my local directory and the
permission are correct, i.e. all files are read only and the locking
system works fine. Therefore I can only think that there must be
something wrong with my settings on my network share.
Does anybody know how svn:needs-lock actually works so I could try and
get to the bottom of this? I mean how does svn:needs-lock change the
permissions of the file to read only? Any help would be much
appreciated as right now I don’t have a clue where to look.
I have installed one fix (see below) in the smb.conf file which fixed
a previous problem when adding new files to the repository:
Path = /svn
Valid users = blah dah spare
Read only = no
Create mask = 0644
Force create mod = 0600
Security mask = 0555
Force securtity mode = 0600
Directory mask = 0770
I don’t think this has anything to do with my problem but it is the
last fix that I had made before these problems began.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-22 16:36:32 CEST