Bug 105697 - grep info files are missing
Summary: grep info files are missing
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: grep   
(Show other bugs)
Version: 7.3
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2003-09-26 16:56 UTC by Mark Harig
Modified: 2007-04-18 16:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-09-29 12:37:39 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Mark Harig 2003-09-26 16:56:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
Many grep 'info' files (at a minimum 'grep.info-1.gz') are missing from the 
grep-2.5.1-1 .rpm distribution.  Effectively, there are no 'info' files for 
grep on RH 7.3.

They are present in grep-2.5.1-7, but this cannot be installed on RH 7.3 
because of dependencies with a later version of GLIBC.

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

How reproducible:

Steps to Reproduce:
1. Run the following command at the shell prompt: info grep
2. This fails because the top-level grep 'info' file cannot find
   files that it references.

Actual Results:  Instead, the manual page for grep is displayed.

Expected Results:  The top-level info page for grep should be displayed.

Additional info:

Comment 1 Tim Waugh 2003-09-29 12:37:39 UTC
This was fixed in Red Hat Linux 8.0 (the release before last).

Comment 2 Mark Harig 2003-09-29 14:38:10 UTC
OK.  Thanks.  I retrieved grep-2.5.1-4 from Red Hat Network.  It installs and 
resolves the problem.  Previously, RHN had only indicated grep-2.5.1-1 (RH 7.3) 
and grep-2.5.1-7 (RH 9) as being available.  When I looked explicitly for the 
grep RPM in the RH 8 release, I was able to find it.

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