Bug 765884 - Using compat-libstdc++ in a Kickstart file failes to install the package.
Summary: Using compat-libstdc++ in a Kickstart file failes to install the package.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: distribution
Version: 5.7
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: RHEL Program Management
QA Contact: Ondrej Hudlicky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-09 16:05 UTC by Leam
Modified: 2014-12-30 11:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:16:43 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Leam 2011-12-09 16:05:58 UTC 
Description of problem:

Putting compat-libstdc++ in the kickstart file gets an error on build. Once the server is created the package is not installed. 

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

RHEL 5.7

How reproducible:

Kickstart with a minimal file set and put compat-libstdc++ in the packages list.

Steps to Reproduce:
1. Build Kickstart File
2. Kickstart Server
3. Check installed packages.
  
Actual results:

No compat-libstdc++ 

Expected results:

has compat-libstdc++ 

Additional info:
Comment 1 RHEL Program Management 2014-03-07 12:46:53 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 2 RHEL Program Management 2014-06-02 13:16:43 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Note You need to log in before you can comment on or make changes to this bug.