It depends on how badly you need it. If you can patch it yourself, do that and submit the patch to the author. I'm assuming you have some build or install mechanism you use that installs known versions of your CPAN modules; just make your fixed version the one that gets installed. If you can get along without it, note in your docs that you didn't use it because it's buggy, so the next person along doesn't try to use it. (Mentioning the link to the open bug would be a nice thing to do, in case the bug gets closed.)

Fixing the bug(s) and sending a pull request to the author would be a mitzvah (and a nice way to get into the committers list).

In reply to Re: Best way to deal with a bug in a CORE Module by pemungkah
in thread Best way to deal with a bug in a CORE Module by boftx

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.