I have met the enemy and they are me.
I displayed the properties again in Tortoise and notice the needs-lock
one was "svn.needs-lock" instead of "svn:needs-lock" with the colon. I
fixed that and now the file is read only as it should be.
Thanks for the ideas.
FG wrote:
> Steve Williams wrote:
>
>> FG wrote:
>>
>>> Bill Williams wrote:
>>>
>>>> I have set the needs-lock property on the file, but when I checkout
>>>> the directory structure the file is located within, the file
>>>> still has read/write permissions.
>>>
>>>
>>> Did you commit the file after changing that property??
>>
>>
>> Did you set the "needs-lock" property or the "svn:needs-lock" property?
>>
> If he is using TortoiseSVN (mentioned earlier), the property should
> show up properly.
>
> I'd test the following tonight, but am about to wrap up and head out
> for dinner with the wife, so I leave it to you...
>
> After checking out the file (after the initial import) - what is the
> status of that property?? If it needs to be reset, do so and then
> commit again. Perform an update or do a checkout on another machine
> or to another directory. See what happens.
>
> Maybe there is something wrong with setting the property on the file
> prior to the import. Which actually kind of makes sense. When you do
> an import, the file is not part of the repository, therefore there is
> no property to set on that file. So you import the files (revision 1)
> and then set your properties (revision 2 with commit).
>
> Something to think about...
>
> Regards,
> Frank
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 6 13:41:02 2006