Using darcs 1.0.9, I pushed from a local darcs 1 repo to a remote darcs 1 repo. 
On the remote server, darcs 2.0.0pre3 (~feb 6th) had been installed as the 
default "darcs". The push repeatably completed without an error message, didn't 
show "Finished applying", didnt't apply the patch and left a lock file in the 
remote repo. Making darcs 1 the default on the remote server made things work 
normally again.

I suspect that this is now fixed, as I fixed a recent bug in applying patches. 
But it might not be, so if you could test this and let me know, that would be
great.  (I'm not resolving yet, because I'm uncertain that I've fixed what went
wrong here, just suspicious that it's the same bug that I fixed today.)

Thanks for the report!

Thanks David. I can still reproduce it with the latest code.

I just tried this out, and successfully used darcs 1.0.9rc1 to push to a remote
server running the latest darcs-2 unstable.  So I'm afraid there may be
something specific going wrong on your server.  :(

David,

Is there a technique we could use to get more debugging output. For example,
maybe there's a way to have the darcs on the server run apply with
"--debug-verbose" and log the results to a file...or back to the user?

  Mark

On Thu, Feb 14, 2008 at 11:06:38PM -0000, Mark Stosberg wrote:
> Is there a technique we could use to get more debugging output. For example,
> maybe there's a way to have the darcs on the server run apply with
> "--debug-verbose" and log the results to a file...or back to the user?

One could definitely add --debug-verbose to the defaults file on the
server, but I can't think of a good way to log the results to a file
(without adding a new flag to darcs, which seems a bit heavy).  Perhaps
just adding --debug-verbose would be enough to trigger this? Another option
would be to try using darcs send and darcs apply to trigger this manually.
Or one could use something like `DARCS_SSH='cat > /tmp/log' darcs push` to
find out what darcs push is trying to send to the remote darcs apply... I
suppose one might need to write a little script to handle this, given how
darcs calls ssh (giving the server as an argument).  And then one could
call apply by hand.
-- 
David Roundy
Department of Physics
Oregon State University

Simon, 

This sounds similar to, but different than what happened in issue672. A
workaround in that case using send and apply rather than "push" caused the patch
apply cleanly. Plus, it gives you the chance to run apply with
"--debug-verbose". I recommend trying that next.

That repo is long gone; I am assuming this was fixed, if not re-open.