Bug 66619 – Unexpected stderr output from "man 1 epic" command

Bug 66619 - Unexpected stderr output from "man 1 epic" command

Summary:	Unexpected stderr output from "man 1 epic" command

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	epic (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-06-12 13:50 EDT by Glen A. Foster
Modified:	2008-05-01 11:38 EDT (History)
CC List:	0 users

See Also:
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:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

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)

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