Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Rebuild required to work correctly with perl 5.12.4
https://bugzilla.redhat.com/show_bug.cgi?id=720744
Summary: Rebuild required to work correctly with perl 5.12.4
Product: Fedora
Version: 15
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: perl-Devel-Cover
AssignedTo: tcallawa(a)redhat.com
ReportedBy: berrange(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: tcallawa(a)redhat.com, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Story Points: ---
Description of problem:
Any attempt to use perl-Devel-Cover in fully updated Fedora 15, results in a
warning printed
This version of Devel::Cover was built with Perl version 5.012003.
It is now being run with Perl version 5.012004.
Attempting to make adjustments, but you may find that some of your modules do
not have coverage data collected. You may need to alter the +-inc, +-ignore
and +-select options.
At the very least, this is obscuring real problems with doing coverage testing
of unit tests, but is also causing potentially incorrect results.
A simple rebuild of the RPM should solve it.
Version-Release number of selected component (if applicable):
perl-Devel-Cover-0.66-3.fc15.x86_64
perl-5.12.4-159.fc15.x86_64
How reproducible:
Always
Steps to Reproduce:
1. $ perl -MDevel::Cover -e ''
2.
3.
Actual results:
This version of Devel::Cover was built with Perl version 5.012003.
It is now being run with Perl version 5.012004.
Attempting to make adjustments, but you may find that some of your modules do
not have coverage data collected. You may need to alter the +-inc, +-ignore
and +-select options.
Expected results:
No scary warning
Additional info:
Same as the previous F14 bug now fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=691451
--
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.