If you can't get the maintainer to update it, post a fixed distribution to CPAN anyway. It won't be indexed but you could ask the modules list to transfer permissions to you. Once you have that, ask PAUSE to reindex it and you're the proud maintainer of a module. Then we all win. Also, filing tickets on RT is nice because that's the public place to write down bug reports so other people can know abou them.

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

In reply to Re: Getting GnuPG.pm to work with gpg > 1.25 by diotalevi
in thread Getting GnuPG.pm to work with gpg > 1.25 by zentara

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.