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

access lock bug with 'svn up FILENAME'

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-10-23 04:05:38 CEST

This is probably simple, so I'm just sending here rather than an issue:

[gstein@roshi cvs2svn]$ svn up
U cvs2svn.py
Updated to revision 3446.
[gstein@roshi cvs2svn]$ svn up -r 3440 cvs2svn.py
U cvs2svn.py
subversion/libsvn_wc/lock.c:407: (apr_err=155005, src_err=0)
svn: Working copy not locked
svn: directory not locked (.)
[gstein@roshi cvs2svn]$ svn up cvs2svn.py
U cvs2svn.py
subversion/libsvn_wc/lock.c:407: (apr_err=155005, src_err=0)
svn: Working copy not locked
svn: directory not locked (.)
[gstein@roshi cvs2svn]$ svn up
At revision 3446.
[gstein@roshi cvs2svn]$ svn up -r 3440 cvs2svn.py
U cvs2svn.py
subversion/libsvn_wc/lock.c:407: (apr_err=155005, src_err=0)
svn: Working copy not locked
svn: directory not locked (.)
[gstein@roshi cvs2svn]$ svn up
U cvs2svn.py
Updated to revision 3446.
[gstein@roshi cvs2svn]$

At the various points, it seems the WC is all right, and the file certainly
reflects the right bits. But that lock thing...

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 23 04:05:53 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.