svn: Working copy not locked

Hi!

I'd just got bitten by an unexpected feature ;-)

I had an old WC on one machine, still pointing to the right repo. So I said
'svn update', and on it went. Until it hit a subdirectory which already held
some unversioned files with the same names as the now-versioned ones. There,
it came to a stop and muttered something about 'Obstructed update'.

OK, so delete the file. Another go. 'Obstructed update' on next file. OK, so
delete the entire tree in this directory and go again... I thought.

But, what the... now I got:
svn: Working copy not locked
svn: directory not locked (Subsystems/JetterCom)

And there I am, plain and out of luck. I can't get this 'resolved' or
'cleanup'ed, it still mumbles the same message.

Interestingly, 'resolve' gives out the warning:
svn: warning: directory not locked (Subsystems/JetterCom)
but I already know this ;-)

So, it seems the reproduction recipe is:

svnadmin create /tmp/test_repo
svn co file:///tmp/test_repo test_wc
cd test_wc
mkdir a_dir
svn add a_dir
svn -m 'test' ci
touch a_dir/a_file
svn add a_dir/a_file
svn -m 'test' ci
svn update -r1
touch a_dir/a_file
svn update
rm -rf a_dir
svn update

... and now, no way to get a_dir back without a co.

Is this an issue? Or already resolved? (I didn't find it...)
BTW, I'm still using 0.25.0 (but we'll upgrade to 0.29.0 tonight, I promise).

Greetings,
        Joerg

-- 
Leading SW developer  - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org