Ken Williams wrote:

On May 7, 2006, at 6:49 AM, Robert Rothenberg wrote:


I'm reminder of one other issue: there are Windows vs Unix end-of-line
issues that it sometimes chokes on.

I've just re-released Pod::Readme without a signature, because the signature
problems are choking up Module::Build users.


Module::Build doesn't do anything with signatures - all it knows how to do is generate a signature file when building a distribution. I'd suspect that the failures have more to do with the version of CPAN or CPANPLUS users have. Or if it's M::B in some way I don't understand, do you have any error output?

 -Ken

Could the problem be in contacting the keyserver?

Just now I manually downloaded and unpacked Module-Build-0.28. I followed the instructions in the SIGNATURE file (which, BTW, appears twice in the MANIFEST -- though apparently without causing error) and got this error message:

[Downloads] 508 $ cd Module-Build-0.28
[Module-Build-0.28] 510 $ cpansign -v
Executing gpg --verify --batch --no-tty --keyserver=hkp://pgp.mit.edu:11371 --keyserver-options=auto-key-retrieve SIGNATURE
gpg: Signature made Fri Apr 28 00:14:21 2006 EDT using DSA key ID B7EF9476
gpg: requesting key B7EF9476 from hkp server pgp.mit.edu
gpg: keyserver timed out
gpg: Can't check signature: public key not found
==> BAD/TAMPERED signature detected! <==


I got the same results with PathTools:

[PathTools-3.18] 518 $ cpansign -v
Executing gpg --verify --batch --no-tty --keyserver=hkp://pgp.mit.edu:11371 --keyserver-options=auto-key-retrieve SIGNATURE
gpg: Signature made Thu Apr 27 23:02:23 2006 EDT using DSA key ID B7EF9476
gpg: requesting key B7EF9476 from hkp server pgp.mit.edu
gpg: keyserver timed out
gpg: Can't check signature: public key not found
==> BAD/TAMPERED signature detected! <==


Since I wasn't attempting to install, these error messages were independent of the actual operation of CPAN.pm or the cpan shell. But do they bear upon the problem I previously reported elsewhere and that RR's users seem to be experiencing?

Thanks.

jimk

Reply via email to