When running darcs apply with --verify, the keyring is treated as path and all
path separators are transformed into /, but gpg for windows doesn't understand
this.  Using full path, with drive-letter, doesn't help.

This is also bug in gpg, and maybe certainly not critical until someone tries to
use host darcs email/other push scheme in Windows.

Transcript follows:
D:\source\haskell\sign>darcs apply -v --verify=d:\source\haskell\sign-ring ..\ad
d-foo.darcs
gpg: error creating keyring `C:/Documents and Settings/eivuokko/Application Data
/gnupg\d:/source/haskell/sign-ring': Invalid argument
gpg: keyblock resource `C:/Documents and Settings/eivuokko/Application Data/gnup
g\d:/source/haskell/sign-ring': file open error
gpg: Signature made 11/23/05 01:01:37 using DSA key ID B9223248
gpg: Can't check signature: public key not found
gpg: error creating keyring `C:/Documents and Settings/eivuokko/Application Data
/gnupg\d:/source/haskell/sign-ring': Invalid argument
gpg: keyblock resource `C:/Documents and Settings/eivuokko/Application Data/gnup
g\d:/source/haskell/sign-ring': file open error
gpg: Signature made 11/23/05 01:01:37 using DSA key ID B9223248
gpg: Can't check signature: public key not found

darcs failed:  Patch bundle not properly signed, or gpg failed.

D:\source\haskell\sign>gpg --batch --no-default-keyring --keyring d:\source\hask
ell\sign-ring --verify ..\add-foo.darcs
gpg: Signature made 11/23/05 01:01:37 using DSA key ID B9223248
gpg: Good signature from "Esa Ilari Vuokko <ei@vuokko.info>"

I'm wondering, would gpg be all right with a path like

C:\foo/bar/baz?

That might be a bit more transparent to code than converting all / to \ on
windows.  On the other hand, I imagine that \ is illegal in filenames on
windows, which might mean that converting all / to \ when we do the system
call would be reasonable...
-- 
David Roundy
http://www.darcs.net

I have patch for this, posted on darcs-devel [1] (There is also
another patch on that email.)  I implemented it simply by
making conversion in this specific case.  I didn't feel
courageous enough to change this behaviour through-out darcs.
(or even just exec)

It's rarely a problem to have / as patch separator, it is  just
some tools, like gnupg that have wierd expectations.  And some
things think / as a commandline switch, but it's mostly non-issue
when quotes are in place.  Converting such switches to \ would
be wrong, tho.

[1] http://www.abridgegame.org/pipermail/darcs-devel/2005-November/003583.html

Looks good to me.  Thanks!
-- 
David Roundy
http://www.darcs.net

fixed in 1.0.6
Tue Nov 29 17:45:33 CET 2005  Esa Ilari Vuokko <ei@vuokko.info>
  * Use \ as path separator for GnuPG in Windows -- makes apply --verify work