Re: svn:needs-lock cannot set files to read only

2009/7/23 dan stead <daniel.stead_at_bt.com>:
> I have an update to my problem and it seems to centre around the
> smb.conf file in particular the line:
>
> force create mode = 0600 which forces all new files created to have
> read and write privileges for the user.
>
> This fix was put into place because of this error message "error
> processing command 'committed' in ... can't move" when trying to
> commit files to SVN:
>
> Toroise SVN
>
>        In directory ******************
>        Error processing command ‘committed’ in  ****************
>        Can’t move
>        ‘W:\**************\.svn\props\*************svn-work’
>        To
>        ‘W:\**************\.svn\prop-base\*************svn-base’;
>        Access is denied
>
>
> By adding this force create mode = 0600 to the smb.conf file for the
> network shared area the commit function correctly.
>
> However, by solving one problem I then created another for myself as
> the force create mode = 0600 forced all the files in my working copy
> to have -rw-r--r-- (read/write access). As I have specified in my
> torviseSVN conifg file that all files are to have the property
> svn:needs-lock ,to stop user from editing a file without acquiring the
> lock for the file, the fix overrides this and makes all files red/
> write. This defies the point of the need lock property and I find
> myself in a catch 22 situation.
>
> To go a bit deeper into the problem the files within the .svn
> directories are created with –r--r--r-- (read only) when the smb.conf
> file does not contain the force create mode = 0600 and is -rw-r--r--
> (read/write) when the force create is present. When I try to move a
> file in windows explorer from .svn/props to .svn/prop-base when the
> files are read only I recive a prompt:
>
> Are you sure you want to move the read-only file ‘text.txt’? Yes/No
>
> But when I try to do the same move when the file is read/write there
> is no prompt and file moves straight away.
>
> Could it be that the tortiseSVN runs into the same prompt when trying
> to do the commit procedure and therefore falls over?
>
> If any could shed any light on this matter it would be most helpful.

All that stuff is done inside the subversion library, not by TortoiseSVN.

> Im currently running samba version 3.0.25a with tortiseSVN 1.6.3 build
> but am in the process of trying to get my sys admin to upgrade the
> samba version in the hope that this error will go away!

From what I remember the SAMBA locking bugs were fixed in a later
release, somewhere around 3.2.3.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2374883
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].