Bug 609484

Summary: openssl man page conatins POD ERRORS
Product: Red Hat Enterprise Linux 6 Reporter: Miroslav Vadkerti <mvadkert>
Component: opensslAssignee: Tomas Mraz <tmraz>
Status: CLOSED CURRENTRELEASE QA Contact: Miroslav Vadkerti <mvadkert>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: openssl-1.0.0-4.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:17:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Miroslav Vadkerti 2010-06-30 12:14:47 UTC
Description of problem:
man openssl contains this message:

POD ERRORS
       Hey! The above document had some coding errors, which are explained
       below:

       Around line 292:
           ’=item’ outside of any ’=over’

       Around line 308:
           You forgot a ’=back’ before ’=head2’


Version-Release number of selected component (if applicable):
openssl-1.0.0-3.el6

How reproducible:
100%

Steps to Reproduce:
1. man openssl
  
Actual results:
POD ERRORS shown in man page

Expected results:
No errors in man page

Additional info:
Looks like this is also in upstream

Comment 2 RHEL Program Management 2010-06-30 12:43:07 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 Miroslav Vadkerti 2010-07-21 09:54:22 UTC
No more POD ERRORS observed in openssl-1.0.0-4.el6 included in compose RHEL6.0-201007015.0

Putting to verified

Comment 5 releng-rhel@redhat.com 2010-11-10 21:17:58 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.