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

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

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Thu, 23 Jul 2009 00:21:13 +0100

2009/7/22 dan stead <daniel.stead_at_bt.com>:
> That’s what happens when you don’t use the spell check. I will amend
> the post.

What I meant was if that spelling error was in the real smb.conf then
the config would not be doing what you expected. I can't tell if the
typo is in your file or just the email.

I would expect you to get the same errors from the SVN command line
client, in which case you could also ask on the subversion users list
and get more answers.

Simon

> On Jul 22, 3:55 pm, Simon Large <simon.tortoise..._at_googlemail.com>
> wrote:
>> 2009/7/22 dan stead <daniel.st..._at_bt.com>:
>>
>>
>> > 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:
>>
>> > [svn]
>> >        Path = /svn
>> >        Valid users = blah dah spare
>> >        Read only = no
>> >        Create mask = 0644
>> >        Force create mod = 0600
>> >        Security mask = 0555
>> >        Force securtity mode = 0600
>>
>> Do you really spell security like that?
>>
>> >        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.
>>
>> 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&dsMessa...
>>
>> To unsubscribe from this discussion, e-mail: [dev-unsubscr..._at_tortoisesvn.tigris.org].- Hide quoted text -
>>
>> - Show quoted text -
>
> ------------------------------------------------------
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2374466
>
> To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
>

-- 
:       ___
:  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=2374618
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-23 01:21:56 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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