Description of problem: If I want to install a perl module rpm (third-party) which requires Carp::Heavy, I'm not able to do, because of this missing dependency. But please have a look: --- snipp --- # rpm -ql perl | grep Carp/H /usr/lib/perl5/5.8.0/Carp/Heavy.pm # --- snapp --- Woho, perl provides this module, but the rpm still doesn't. It seems to be the same problem like bug #128507 from Fedora Development. Version-Release number of selected component (if applicable): perl-5.8.0-88.4 Actual results: The following (merged from Fedora Development) solves that problem for me: --- snipp --- --- perl.spec 2003-09-15 15:59:17.000000000 +0200 +++ perl.spec.rsc 2004-08-12 16:21:29.000000000 +0200 @@ -265,6 +265,8 @@ Provides: perl(utf8_heavy.pl) Provides: perl(validate.pl) +Provides: perl(Carp::Heavy) + # These modules appear to be missing or break assumptions made by the # dependency analysis tools. Typical problems include refering to # CGI::Apache as Apache and having no package line in CPAN::Nox.pm. I @@ -660,6 +662,9 @@ %endif %changelog +* Thu Aug 12 2004 Robert Scheck <redhat> +- add 'Provides: Carp::Heavy' to fix a dependency problem + * Mon Sep 15 2003 Chip Turner <cturner> 2:5.8.0-88.4 - rebuild to include security fixes from errata --- snapp --- Expected results: Use of the patch for the next perl rebuild for RHEL3 ;-) Additional info: I marked this issue only with a low priority, because RHEL3 doesn't have an perl module rpm which requires Carp::Heavy, so only third- party perl module rpms can cause this problem. Nevertheless it is a issue which should be fixed.
I'd like to see this fixed as well.
OK, the next perl release for RHEL-3: perl-5.8.0-90.2 now 'Provides: perl(Carp::Heavy)' .
Jason, I would like to close this bug report, as I verified it in Errata of perl-5.8.0-90.4, but Bugzilla is telling me: "You tried to change the Status field from MODIFIED to CLOSED, but only the owner or submitter of the bug, or a sufficiently empowered user, may change that field." - in fact I am the submitter of the bug...looks like a Bugzilla bug? ;-)