It seems as if when you pass an absolute path to 'darcs get --context', it
doesn't recognize it as an absolute path, and appends it to the working
directory.  The result is something like this:

darcs.EXE:
C:/cygwin/home/kevint/tsrc/Buildbot/_trial_temp/slavebase/vc-dir/C:/cygwin/home/kevint/tsrc/Buildbot/_trial_temp/slavebase/vc-dir/.darcs-context:
openBinaryFile: invalid argument (Invalid argument)

using the win32 build of darcs 1.0.7.

keturn,

Thanks for the report. Are you able to test again with Darcs 1.0.9 or one of the
2.0 pre-release builds from the wiki?

Even though I'm not very literate in Haskell, I think I confirmed this bug in
the source code. In src/Darcs/Commands/Get.lhs, these lines look to me like a
hard-coded assumption that an absolute path would always start with: "/":

  let opts = fix_context orig_opts
      fix_context o@(Context ('/':_):_) = o
      fix_context (Context f:os) = Context (former_dir++"/"++f):os
      fix_context (o:os) = o : fix_context os
      fix_context [] = []

On Thu, Jan 24, 2008 at 02:32:01 -0000, Mark Stosberg wrote:
>   let opts = fix_context orig_opts
>       fix_context o@(Context ('/':_):_) = o
>       fix_context (Context f:os) = Context (former_dir++"/"++f):os
>       fix_context (o:os) = o : fix_context os
>       fix_context [] = []

Hmm, darcs does have a more platform-independent is_absolute function
(Darcs.Url, I think) we could use.  Want to try plugging it in?

Is there anyone on darcs-devel that could help with what looks an easy bug fix
for Windows? See the issue tracker link online for more context:

On Thu, Jan 24, 2008 at 02:32:01 -0000, Mark Stosberg wrote:
>   let opts = fix_context orig_opts
>       fix_context o@(Context ('/':_):_) = o
>       fix_context (Context f:os) = Context (former_dir++"/"++f):os
>       fix_context (o:os) = o : fix_context os
>       fix_context [] = []

Hmm, darcs does have a more platform-independent is_absolute function
(Darcs.Url, I think) we could use.  Want to try plugging it in?

I see that patches were committed for this, and I just sent a regression test,
so I'm marking it resolved for now. The regression test should smoke out the
issue if it is still present.