Re: Working copy not locked

Stephen Clouse <stephenc@theiqgroup.com> writes:

> After updating to r3261 (both client and server) I am now getting this
> (egregiously unhelpful) error message:

And so you provided an (egregiously unhelpful) bug report :)

What did you upgrade from?
Do the Subversion regression tests pass?

> stephenc@stephenc Core $ svn update
> At revision 64.
> subversion/libsvn_wc/lock.c:407: (apr_err=155005, src_err=0)
> svn: Working copy not locked
> svn: directory not locked (libiqgcore)
>
> It happens on all repositories (although the directory is different, obviously).

What did you do before running this command?
Does 'svn st' work?
Does 'svn info' work?
This is a working copy error, what does "all repositories" mean?

Somewhere you must have a Subversion working copy, since you have
r3261, does 'svn update' work there?

> svn log is now completely hosed (it gives the same error):

Does 'svn log URL' rather than 'svn log wc_path' work?

> stephenc@stephenc Core $ svn log
> subversion/libsvn_wc/lock.c:407: (apr_err=155005, src_err=0)
> svn: Working copy not locked
> svn: directory not locked (/home/stephenc/devel/IQGroup/Core/libiqgcore)
>
> After perusing the list archives, I've tried svn cleanup (about ten different
> variations of it), and recreating the repository. No luck.

Do you mean that 'svn cleanup' failed with a "not locked" error, or
that it had no effect?

What does "recreating the repository" mean? Does it mean you ran
'svnadmin create', 'svnadmin load', and then 'svn co' to get a new
working copy? Does it imply that 'svn checkout' works?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org