hi!

try this:

$ darcs get --lazy http://common-lisp.net/project/cl-dwim/darcs/cl-dwim/
Unapplicable patch:
Sun Apr 27 12:30:21 CEST 2008  levente.meszaros@gmail.com
  * Remove obsolete tests.

darcs failed:  Cannot remove non-empty file ./test/model/audited-object.lisp

$ darcs --version
2.0.1rc1 (2.0.1rc1 (release candidate 1))

hth,

Thanks for the bug report.

This sounds like another (!) instance of issue693, http://bugs.darcs.net/issue693

Fortunately, darcs repair now fixes those patches.  We still don't know why they
are being generated.  We would be much obliged if you could make a copy of your
repository before fixing it and help us to reproduce the conditions that led to
the bad patch being generated in the first place.  Otherwise, just darcs repair
and move on :-(

>  Fortunately, darcs repair now fixes those patches.  We still don't know why they
>  are being generated.  We would be much obliged if you could make a copy of your

for some background info: i remember seeing darcs having rouble with
file removals/renames where it left the repo in an inconsistent state.
it was rather easy to overcome, so easy, that i just ignored it...
could be these (bogus?) patches are still lingering in the repo and
causing headache to darcs2.

also note, that i usually built darcs from the stable branch from time to time.

>  repository before fixing it and help us to reproduce the conditions that led to
>  the bad patch being generated in the first place.  Otherwise, just darcs repair
>  and move on :-(

err, i don't understand it. if it helps, i can package up the
repository and make it downloadable - just let me know.

but if you mean a test case that reproduces such a repo... that would
be waaaay too much pain. i'm happy enough that darcs repair solves it
now... :)

btw, meanwhile i get the repo using darcs 1.0.9 and it worked fine.