Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
texlive contains shell scripts that use 'grep' and 'awk', for example:
/usr/bin/texhash
/usr/bin/texconfig
/usr/bin/updmap
But the package texlive doesn't depend on sed nor awk.
It causes error messages in some cases:
...
Installing : texlive-2007-56.el6.s390x 87/101
Installing : texlive-dvips-2007-56.el6.s390x 88/101
...
Installing : tex-kerkis-2.0-23.el6.noarch 101/101
/usr/bin/texhash: line 17: sed: command not found
/usr/bin/texhash: line 42: sed: command not found
/usr/bin/texhash: line 123: sed: command not found
/usr/bin/texhash: line 123: sed: command not found
/usr/bin/texhash: line 123: sed: command not found
/usr/bin/texhash: line 123: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/texconfig: line 146: sed: command not found
/usr/bin/updmap: line 389: awk: command not found
/usr/bin/updmap: line 219: sed: command not found
/usr/bin/updmap: line 219: sed: command not found
...
Version-Release number of selected component (if applicable):
texlive-2007-56.el6
How reproducible:
always
Steps to Reproduce:
1. yum --installroot=/root/new_install_root install tex-kerkis
Actual results:
error messages from texhash, texconfig and updmap scripts: sed and awk commands not found
Expected results:
texlive depends on grep and awk, no error when running texlive scripts
Comment 1RHEL Program Management
2011-07-06 01:13:19 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. If you would like it considered as an
exception in the current release, please ask your support
representative.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/