(By the way, I opened a new ticket -- http://bugs.darcs.net/issue801  
-- for this before I realized that it looks the same as the resolved  
issue687.)

On Apr 18, 2008, at 2:38 PM, Zooko wrote:
>
>
> Argh, now I attempted to reproduce it by switching back to the
> earlier version of darcs -- at least I *think* it was the same darcs
> executable that I used earlier, and it emits the same version string,
> but now the problem didn't happen:

I just confirmed that there are only two darcs executables on this  
system, so I was definitely reusing the same "darcs 2.0.0 + -1" when  
I ran the test the third time as when I did it the first time and  
experienced the bug.

Regards,

Zooko