Bug 722250

Summary: pango post-install uses sed but does not list sed as a dependency
Product: Red Hat Enterprise Linux 5 Reporter: Matt Rogers <mrogers>
Component: pangoAssignee: Akira TAGOH <tagoh>
Status: CLOSED WONTFIX QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-07 01:29:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 743405, 1002709    

Description Matt Rogers 2011-07-14 18:22:25 UTC 
Description of problem:

The post-install for pango uses sed, but pango does not depend on sed.  With the default install, sed will happen to be installed before pango, but when additional packages are installed, sometimes (semi-randomly based on how many packages there are), pango will be installed before sed and the pango.modules will be written to the wrong directory. The problem manifests for the customer when creating custom kickstarts.

This was fixed in RHEL 6 at https://partner-bugzilla.redhat.com/show_bug.cgi?id=593073 , and I am opening this for the fix to be included in RHEL5 as well.

RHEL 5.6's version of pango does not list sed as a dependency.

# rpm -q --requires pango| grep sed
rpmlib(CompressedFileNames) <= 3.0.4-1

# rpm -q pango
pango-1.14.9-8.el5_6.2
Comment 1 RHEL Program Management 2011-07-14 18:37:25 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 2 RHEL Program Management 2011-09-23 00:48:41 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 3 RHEL Program Management 2012-06-12 01:24:38 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 6 RHEL Program Management 2013-05-01 07:10:42 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 8 Andrius Benokraitis 2013-10-07 01:29:17 UTC 
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.