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

svn:needs-lock fails to remove read-only flag

From: Ward, Arthur \(Mission Systems\) <Arthur.Ward_at_ngc.com>
Date: 2006-06-29 18:42:33 CEST

I believe we have found a bug in TortoiseSVN's handling of the
svn:needs-lock property -- it doesn't set the file back to read-write
when the needs-lock is removed during an update.

Affected: TortoiseSVN 1.3.5 Build 6804

Steps to reproduce:
1. Checkout a file having the "svn:needs-lock" property.
2. Using a different WC, remove the needs-lock and commit.
3. Update in the original WC. Observe that needs-lock is removed, but
the file remains marked read-only.

Using the command-line svn client, we see that the file returns to
read-write (svn 1.2.3 on Linux), which is what we expected to happen.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jun 29 18:42:49 2006

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.