Bug 217300 - perl(:MODULE_COMPAT_5.8.0)
Summary: perl(:MODULE_COMPAT_5.8.0)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: perl
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Robin Norwood
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-26 19:01 UTC by Christopher McCrory
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 18:39:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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