Bug 62525

Summary: "man builtins" gets an error.
Product: [Retired] Red Hat Linux Reporter: Rich Morin <rdm>
Component: bashAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-09-26 01:55:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Rich Morin 2002-04-02 03:12:00 UTC
From Bugzilla Helper:

User-Agent: Mozilla/4.0 (compatible; MSIE 5.13; Mac_PowerPC)



Description of problem:

Typing "man builtins" generates the error
"<standard input>:14: realpath on `bash.1' failed: No such file or directory"



This seems to be caused by the fact that builtins.1.gz contains
the line ".so bash.1", but there is no such file (only bash.1.gz).
My suspicion is that man(1) can handle a ".so" line when it is
the only line in the file, but has problems when there is some
preceding troff text (i.e., I think some kludge is incomplete. :-).



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





How reproducible:

Always



Steps to Reproduce:

1.man builtins

2.

3.

	



Actual Results:  <standard input>:14: realpath on `bash.1' failed: No such 
file or directory

BASH_BUILTINS(1)                                 BASH_BUILTINS(1)



NAME

       bash,  :,  .,  alias,  bg, bind, break, builtin, case, cd,

       command, continue, declare, dirs,  disown,  echo,  enable,

...



Expected Results:  The man page for bash(1) should have followed the 
page I saw.



Additional info:

Comment 1 Tim Waugh 2002-10-07 11:15:39 UTC

*** This bug has been marked as a duplicate of 19555 ***