[Bug 481147] New: cpan2rpm doesn't work with latest Pod::Text

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: cpan2rpm doesn't work with latest Pod::Text

https://bugzilla.redhat.com/show_bug.cgi?id=481147

           Summary: cpan2rpm doesn't work with latest Pod::Text
           Product: Fedora
           Version: 10
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: low
          Priority: low
         Component: cpan2rpm
        AssignedTo: gavin.henry at gmail.com
        ReportedBy: gavin.brown at uk.com
         QAContact: extras-qa at fedoraproject.org
                CC: fedora-perl-devel-list at redhat.com,
                    fedora-triage-list at redhat.com, gavin.henry at gmail.com
    Classification: Fedora
          Clone Of: 279251


+++ This bug was initially created as a clone of Bug #279251 +++

Description of problem:

The latest version of Pod::Text from CPAN is from RRA/podlators-2.2.2.tar.gz

Pod::Text no longer derives from Pod::Parser so the method 'interpolate' does
not exist.  As near as I can tell, this is the only method used in cpan2rpm, so
Pod::Text can be changed to Pod::Parser in the two places it appears.  This is
what I did locally and it now works for me.

Version-Release number of selected component (if applicable):

cpan2rpm-2.028-2.fc8.1.noarch

How reproducible:

update Pod::Text via cpan.
Run cpan2rpm for some module (any will do...)

Actual results:

[...]
-- module: /var/cache/cpan/build/libwww-perl-5.808-baHtIL --
Metadata retrieval
Can't locate object method "interpolate" via package "Pod::Text" at
/usr/bin/cpan2rpm line 522.
-- Done --


Expected results:

No failure from above.

Additional info:

--- Additional comment from fedora-triage-list at redhat.com on 2008-05-14
10:14:55 EDT ---

This message is a reminder that Fedora 7 is nearing the end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining and
issuing updates for Fedora 7. It is Fedora's policy to close all bug reports
from releases that are no longer maintained. At that time this bug will be
closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to
fix it in a currently maintained version, simply change the 'version' to a
later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may
not be able to fix it before Fedora 7 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version of
Fedora please change the 'version' of this bug. If you are unable to change the
version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Fedora release includes newer upstream software that fixes bugs or makes them
obsolete. If possible, it is recommended that you try the newest available
Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure
it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from fedora-triage-list at redhat.com on 2008-06-16
22:19:58 EDT ---

Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.