On 4/8/06, ListMan <listman@burble.net> wrote:
>
> hi all, i'm getting some strange behavior from svn 1.3.1 (fsfs
> backend db)
>
>
> steve@pacifica 15> svn unlock file1
> svn: 'file1' is not locked in this working copy
>
> steve@pacifica 16> svn lock file1
> svn: Path '/trunk//local/file1' is already locked by user 'steve' in
> filesystem '/repos/svn/mainRepos/db'
>
> svn cleanup doesn't have any effect, i get the same behavior after
> running it
>
> does anyone have an idea why this file seems to be "stuck" - does
> this happen alot with other peoples svn repositories?
The file appears to have been locked from another working copy, or
something has been done to make the current working copy lose it's
lock token. You should be able to break the lock by running 'svn
unlock --force file1'.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 9 02:42:58 2006