Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 66619

Summary: Unexpected stderr output from "man 1 epic" command
Product: [Retired] Red Hat Linux Reporter: Glen A. Foster <glen.foster>
Component: epicAssignee: Jeremy Katz <katzj>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-12-29 03:14:31 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Glen A. Foster 2002-06-12 13:50:50 EDT
Description of Problem: Something is not right with the epic.1 man-page.  If you
run the command "man 1 epic 2> stderr", there's data in the file "stderr".

Version-Release number of selected component (if applicable):
# rpm -qf $(which epic)
epic-1.0.1-6

How Reproducible: 100%

Steps to Reproduce:
1. man 1 epic 2> stderr

Actual Results: contents are as follows:
# cat stderr
mdoc warning: Empty input line #298
mdoc warning: Empty input line #306
mdoc warning: list open at EOF!  A .Bl directive has no matching .El

Expected Results: empty stderr output

Additional Information:
This also makes the man-page output for epic.1 empty
Comment 1 Jeremy Katz 2002-12-29 03:14:31 EST
This is something that will need to be fixed upstream as it doesn't affect the
functionality at all (man 1 epic still works perfectly fine for me)