Re: another working copy not locked

"Wolfgang Schnerring" <wosc@wosc.de> writes:

> I'm running an SVN-repository over HTTP. (svn-0.14.3, rev 3216; httpd-2.0.43)
> Checkout works fine, but there are some strange things happening:
> $ svn log
> subversion/libsvn_wc/lock.c:407: (apr_err=155005, src_err=0)
> svn: Working copy not locked
> svn: directory not locked (/path/to/first/directory/in/working/copy)

There were (and perhaps still are) some bugs storing authentication
data in the working copy. Is your repository password protected?
Does 'svn log --no-auth-cache' work? If so then upgrading to rev 3340
or later may fix the problem.

> $ svn up
> At revision NNNN.
> subversion/libsvn_wc/lock.c:407: (apr_err=155005, src_err=0)
> svn: Working copy not locked
> svn: directory not locked (alphab_first_dir_in_wc)

Could be the auth. data again. Does 'svn st -u' work? What does it
show?

> but then again,
> $ svn log http://url.of.repos/
> works just fine

This doesn't attempt to to store auth data.

> "svn cleanup" doesn't change the situation.

It's not relevant for these errors.

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