The following process always leaves a stale lock file:

1. darcs record in repo A, leave it in the state of editing the patch  
description
2. darcs push from another computer to repo A, leave it in the staet  
of "waiting for lock"
3. finish the patch description in repo A

Now the push proceeds, but in this case I get "Apply failed!" (is  
that the way that darcs-2 reports conflicts?).

Now there is a leftover lock file in repo A.

So actually maybe there is a bug here and darcs-2 is not intended to  
write "Apply failed!" and leave a lock file behind...

Regards,

Zooko

Thanks, for the bug report, but alas, I've been unable to reproduce this! When I
do this, I get:

Backing up ./build.xml(-darcs-backup0)
There are conflicts in the following files:
./build.xml

darcs failed:  Refusing to apply patches leading to conflicts.
If you would rather apply the patch and mark the conflicts,
use the --mark-conflicts or --allow-conflicts options to apply
These can set as defaults by adding
 apply mark-conflicts
to _darcs/prefs/defaults in the target repo.
Apply failed!

And there's no lock in either repository afterwards.  Perhaps this is a bug that
has already been fixed in the most recent darcs-unstable?

David