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

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

From: Jonathan Leffler <jleffler_at_us.ibm.com>
Date: 2002-06-19 22:11:41 CEST

OK - svn cleanup did the trick. The residual question is "should I have
had to do that", to which I don't know the answer but it doesn't feel quite
right if that is necessary just because of an interrupt.

Jonathan Leffler (jleffler@us.ibm.com)
STSM, Informix Database Engineering, IBM Data Management Solutions
4100 Bohannon Drive, Menlo Park, CA 94025
Tel: +1 650-926-6921   Tie-Line: 630-6921
      "I don't suffer from insanity; I enjoy every minute of it!"
                      Collins-Sussman          To:       Jonathan Leffler/Menlo Park/IBM@IBMUS                                         
                      <sussman@collab.n        cc:       SVN Dev List <dev@subversion.tigris.org>, users@subversion.tigris.org         
                      et>                      Subject:  Re: Subversion 0.13.0 [Pre-Alpha] released - a report on successes and        
                      Sent by:                  problems                                                                               
                      06/19/02 12:19 PM                                                                                                
"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
> 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 22:09:26 2002

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