Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 136496 - perl and perl-Time-HiRes: perl-Time-Hires no longer needed
perl and perl-Time-HiRes: perl-Time-Hires no longer needed
Product: Fedora
Classification: Fedora
Component: perl (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Chip Turner
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-10-20 11:22 EDT by Jose Pedro Oliveira
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-29 16:41:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jose Pedro Oliveira 2004-10-20 11:22:13 EDT
Description of problem:
Perl 5.8.5 (and 5.8.4) already includes a more recent version
of Time::HiRes than the one shipped as perl-Time-HiRes

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

How reproducible:

Additional info:

Perl distro      Time::HiRes core module
v5.8.4            v1.59
v5.8.5            v1.59

perl-Time-HiRes package
fedora core 3 test 3 ships with perl-Time-HiRes-1.55-3.src.rpm.

Patch to perl.spec
The following line must be removed from the perl.spec:
find $RPM_BUILD_ROOT -name '*HiRes*' | xargs rm -rfv

Related bugzilla entry: 136494
Comment 1 Jose Pedro Oliveira 2005-01-27 22:33:00 EST
This also applies to rawhide (perl 5.8.6).

See also #136494, and #141100.
Comment 2 Chip Turner 2005-01-29 16:41:48 EST
CPAN is already up to 1.66.  the reason we explicitly remove it from perl is because it 
updates frequently upstream.  the correct solution is to upgrade the separate perl-Time-
HiRes package, which will be done sometime in the next week or so., along with other perl 

marking this particular bug as deferred, but only because I'll fix it as part of a separate set 
of updates

Note You need to log in before you can comment on or make changes to this bug.