Rich Drewes <drewes@interstice.com> writes:
> [drewes@cortex-0 newn48]$ svn update
> subversion/libsvn_wc/log.c:289: (apr_err=155009, src_err=0)
> svn: Problem running log
> svn: in directory .
> subversion/libsvn_wc/log.c:1155: (apr_err=155009, src_err=0)
> svn: start_handler: error processing command 'merge' in .
> subversion/libsvn_wc/log.c:436: (apr_err=155005, src_err=0)
> svn: Working copy not locked
> svn: svn_wc_merge() returned an unexpected error
> subversion/libsvn_wc/lock.c:363: (apr_err=155005, src_err=0)
> svn: directory not locked ()
>
> There are a bunch of lock files left hanging around. I don't think
> anything can save this working directory--not even manual deletion of
> lock files; user drewes will have to check out a new copy, reintegrate
> changes, and try again.
>
> This is on subversion-r2092g.tar.gz.
>
> Anyone know what is going on here?
svn r2092! Yeesh, that's from last *May*!
Isn't this an old bug, Philip? Some locking bug, or one that has to
do with running update in "."?
Rich -- try running 'svn cleanup'. And please upgrade to the latest
svn client.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 12 20:17:49 2002