Well, it's odd that darcs 2.7 doesn't seem to complain of any error. I
don't want to speculate on what's going on with the repository. I can
say that it does not occur with darcs 2.3.1, 2.4.3, or 2.5.0; so I'll
guess that the version that's up online is the fixed repository.
Meanwhile, *this* particular ticket (split from its cousin) is really
just about the error reporting.
So I think the main task at hand is to look into the code to find out if
darcs check is [A] fixing something when it shouldn't be, or [B]
hopefully just erroneously reporting that it's doing so
There's also another task, come to think of it, which isn't so easy.
We ideally need some sort of minimal test case with a deliberately
broken repository (one that has a rmfile patch on a non-empty file). I
can't think of any easy way to generate such a repository (it sounds
like hashed repositories would make it super-tedious to hand-edit a
patch). Maybe there's one lying around in tests/, or somebody on darcs-
devel can help you make one.
|