Bug 217300

Summary: perl(:MODULE_COMPAT_5.8.0)
Product: Red Hat Enterprise Linux 3 Reporter: Christopher McCrory <chrismcc>
Component: perlAssignee: Robin Norwood <robin.norwood>
Status: CLOSED WONTFIX QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: perl-maint-list
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 18:39:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christopher McCrory 2006-11-26 19:01:03 UTC
Description of problem:
( enhancement)

perl rpm does not provide perl(:MODULE_COMPAT_5.8.0)

Version-Release number of selected component (if applicable):
perl-5.8.0-94.EL3

How reproducible:
sometimes

Steps to Reproduce:
1. taroon.server.shell> rpmbuild --rebuild
http://mirrors.kernel.org/fedora/core/updates/testing/5/SRPMS/spamassassin-3.1.7-1.fc5.src.rpm
2. rpm -Uvh spamassassin-3.1.7-1.i386.rpm
3. error: Failed dependencies:
        perl(:MODULE_COMPAT_5.8.0) is needed by spamassassin-3.1.7-1

  
Actual results:
error: Failed dependencies:
        perl(:MODULE_COMPAT_5.8.0) is needed by spamassassin-3.1.7-1


Expected results:
gets updated

Additional info:
newer versions of perl in RHEL and fedora provide perl(:MODULE_COMPAT_$version)
It would be nice if the RHEL3 build of perl also provided that also.
Some of us back compile newer versions of various perl software ( like
spamassassin); being able to "rpmbuild --rebuild ..." rather than download, edit
, rpmbuild ... would be nice.

thanks

Comment 1 RHEL Program Management 2007-10-19 18:39:53 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.