Bug 712844 - texlive should depend on grep and awk
Summary: texlive should depend on grep and awk
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: texlive
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Than Ngo
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-13 11:09 UTC by Jan Stodola
Modified: 2017-12-06 12:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:11:52 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jan Stodola 2011-06-13 11:09:34 UTC
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 1 RHEL 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.

Comment 5 Than Ngo 2013-07-15 08:44:38 UTC
it's easy fix, devel ack

Comment 12 Jan Kurik 2017-12-06 12:11:52 UTC
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/


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