Local lock token corrupted by update?

We have an issue where the local lock on a file will break with an SVN
update. It would appear that the local lock token is corrupted in some
manner. Updating just the file didn't seem have an effect but updating
anything higher up the folder chain did every time. The output of the
update distinctly says Lock Broken. The repository, however, still believes
you have the lock. What this means is that when you go to get-lock again,
you can't because the repository (correctly) believes you already have it.
The only action available is to steal your own lock.

We have set these properties in the local Subversion configs.

enable-auto-props = yes

*.* = svn:needs-lock=*

Subversion server is version 1.6.15

This occurred with:

1.7 checkouts upgraded to 1.8

Full fresh checkout on 1.8

Using Tortoise SVN clients:

1.8.1 release

1.8 RC build. (1.8.0.24461)

1.8 nightly release (1.8.99.24559)

A downgrade to 1.7 and a full checkout saw the problem disappear.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3061220

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-07-25 05:25:16 CEST