Re: Subversion 0.13.0 [Pre-Alpha] released - a report on successes and problems

"Jonathan Leffler" <jleffler@us.ibm.com> writes:

> Sorry if I'm boring the pants off everyone - tell me to stop when
> necessary. Is any of this conversation of any help?
>
> I tried the concurrent update example again, and it might be 'just' a
> timing problem. The result the second time was:
>
> $ svn up & sleep 1 && svn up
>
> subversion/libsvn_wc/lock.c:47
> svn_error: #21040 : <Attempted to lock an already-locked dir>
> working copy locked: ./subversion/tests/libsvn_delta
>
> I'd regard that as a reasonable error message - in line with your
> expectations, too.

Excellent.

> When I repeated the exercise again (no updates waiting), then both
> completed without error - though there was some rattling on the disk drive.
> The problem occurred on my system when there was some work to be done
> fetching a new revision.

That makes sense, too. Lockfiles are only dropped into directories
when their contents are being actively "patched up" to new revisions.
If you run 'svn up' on a fully up-to-date working copy, I don't
believe any lockfiles are ever created at all.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 20 01:13:22 2002