Problem with switch and svn:needs-lock

[Mark Phippard <Ma...@softlanding.com>]

If your WC has a file with the svn:needs-lock property set and you then 
switch your WC to a branch where that file does not have that property. 
The property is removed in the WC but the read-only attribute is not 
removed from the file.

This causes problems in Subclipse, and somewhat also TortoiseSVN, since we 
both decorate files based on the read-only attribute.  In the case of 
Subclipse, the presence of the read-only attribute causes Eclipse to 
present the user with the Subclipse Lock UI -- a good thing.  However, we 
are then relying on the svn lock command to remove the read-only 
attribute, which it doesn't in this case.  It would be nice as a fail-safe 
if it could do that.

This should be reproduction recipe.  I did it on Windows, so this may not 
be exactly right.

svn mkdir -m "" url://repos/trunk
svn co url://repos/trunk test_wc
cd testwc
touch foo
svn add foo
svn ci -m ""
svn copy -m "" . url://repos/branch 
svn propset svn:needs-lock foo
svn ci -m "" 
svn switch url://repos/branch

At this point, foo will not have the property, but it will be read-only.

Again, as an additional requuest it would be nice at this point if:

svn lock foo

Would remove the read-only attribute even though the svn:needs-lock 
property does not exist.

Thanks

Mark







_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Problem with switch and svn:needs-lock

[Mark Phippard <Ma...@softlanding.com>]

"Peter N. Lundblad" <pe...@famlundblad.se> wrote on 05/19/2005 08:55:08 
AM:

> On Fri, 13 May 2005, Mark Phippard wrote:
> 
> > If your WC has a file with the svn:needs-lock property set and you 
then
> > switch your WC to a branch where that file does not have that 
property.
> > The property is removed in the WC but the read-only attribute is not
> > removed from the file.
> >
> 
> I'm not sure if anyone answered to this. If not, could you file this as 
an
> 1.2.1 issue?

OK.

http://subversion.tigris.org/issues/show_bug.cgi?id=2306

I wasn't sure how to make it a "1.2.1" issue.  I set the milestone to 
1.2.x.  I also added the subclipse and tortoisesvn keywords since this 
effects the UI of those projects.

Also, 1.2.x needs to be added as a valid value in version.

Thanks

Mark


_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Problem with switch and svn:needs-lock

["Peter N. Lundblad" <pe...@famlundblad.se>]

On Fri, 13 May 2005, Mark Phippard wrote:

> If your WC has a file with the svn:needs-lock property set and you then
> switch your WC to a branch where that file does not have that property.
> The property is removed in the WC but the read-only attribute is not
> removed from the file.
>

I'm not sure if anyone answered to this. If not, could you file this as an
1.2.1 issue?

thanks,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org