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

Re: Lock problem

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-06-23 13:53:57 CEST

On Jun 23, 2005, at 4:47 AM, Anthony Muller wrote:
>
> * Now try to look at the lock:
> ...> cd project
> .../project> svn status -u -v project.xml
> 0 63 63 anthony project.xml
> Status against revision: 63
>
> As you can see, status information is not correct be cause I looked
> the file.
>

You destroyed a whole chunk of working copy, and then 'svn update'
recreated it.

But this means you also destroyed the lock-token stored in the
working copy. 'svn update' will refetch the missing directory, but
it won't refetch your lock-token. That's why you no longer see a 'K'
in status.

To refetch the lock-token, you need to steal the lock back: svn lock
--force.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 23 13:57:07 2005

This is an archived mail posted to the Subversion Users mailing list.