Here's a darcs failure I recieved today...

darcs get --partial --repo-name=depends/filepath http://www.cs.york.ac.uk/fp/darcs/filepath
Copying patch 78 of 78... done!
Applying patch 78 of 78... done.
darcs: bug in darcs!
Impossible case at PatchRead.lhs:56 compiled 08:35:51 Oct 13 2006
Please report this to bugs@darcs.net,
If possible include the output of 'darcs --exact-version'.

...I was having problems building the YHC haskell compiler, which I had
downloaded with darcs-1.0.3 and it was suggested that I upgrade to a
newer darcs, which is how I got this error.  Here's the output of...

~/haskell/YHC/yhc$ darcs --exact-version
darcs compiled on Oct 13 2006, at 08:41:26
# configured Fri Jun 16 14:55:21 EDT 2006
./configure --no-create --no-recursion

Context:

[TAG 1.0.8
Tommy Pettersson <ptp@lysator.liu.se>**20060616160213] 

...I'm assuming that this is caused by some incompatability between
1.0.3 and 1.0.8.  Hope this is of help.

Greg Buchholz

Hmm... I tried to reproduce this, but darcs get worked fine for me

$ mkdir -p foo/depends
$ cd foo
$ darcs get --partial --repo-name=depends/filepath http://www.cs.york.ac.uk/fp/darcs/filepath
Copying patch 78 of 78... done!
Applying patch 78 of 78... done.
Finished getting.

$ darcs --version
1.0.8 (release)

I find this odd.  We're using the same darcs version.  I'm not sure what
other variables might be in play here.  I've tried this on both my Mac
and my Linux virtual machine.

Any ideas?

Eric Kow wrote:
> 
> Eric Kow <eric.kow@gmail.com> added the comment:
> 
> Hmm... I tried to reproduce this, but darcs get worked fine for me
> 
> I find this odd.  We're using the same darcs version.  I'm not sure what
> other variables might be in play here.  I've tried this on both my Mac
> and my Linux virtual machine.
> 
> Any ideas?

    I started out with a previous version of darcs, 1.0.3, then when
that didn't work, I upgraded to a newer version.  This then caused the
failure.  I'm assuming that there was some inconsistent partial result
from the 1.0.3 get, which confused 1.0.8.  It's probably nothing to
worry about, but I thought I'd report the bug, since it asked me to ;-)

Greg Buchholz

This is on Windows, right?  Deferring until we sort out issue364

Marking as duplicate now that we can.  See issue364.  Thanks.

haskell,

Do you experience this issue consistently? Does it still happen for you? I
wonder if doing a "darcs init" followed by a "darcs pull -a" is a workaround. 

   Mark