Re: Subversion 0.13.0 [Pre-Alpha] released - a report on successes and problems

"Jonathan Leffler" <jleffler@us.ibm.com> writes:

> Apologies - I didn't want to screw up my working copy, and didn't
> appreciate that the problem was different.
>
> $ cd subversion-r2263
> $ svn update
> U ./build.conf
> U ./subversion.dsw
> U ./build/buildcheck.sh
> U ./build/gen_base.py
> U ./subversion/include/svn_fs.h
> U ./subversion/include/svn_sorts.h
> U ./subversion/include/svn_client.h
> ^C
> $ svn update
>
> subversion/libsvn_wc/lock.c:47
> svn_error: #21040 : <Attempted to lock an already-locked dir>
> working copy locked: ./subversion/include
> $
>
> I have now screwed it up for you...is there a way to fix this on my working
> copy, or do I have to checkout from scratch?

Run 'svn cleanup'. This effectively runs any logs that were left
around, removes working copy locks.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 19 21:22:00 2002