Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1611304 - Man page scan results for gfs2-utils
Summary: Man page scan results for gfs2-utils
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gfs2-utils
Version: 29
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Andrew Price
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FedoraManpagescan
TreeView+ depends on / blocked
 
Reported: 2018-08-02 08:33 UTC by Maryna Nalbandian
Modified: 2019-10-15 14:32 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-15 14:32:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Logs (3.97 KB, text/plain)
2018-08-02 08:33 UTC, Maryna Nalbandian
no flags Details

Description Maryna Nalbandian 2018-08-02 08:33:13 UTC
In order to improve usability of packages in Fedora, project Man Page Scan was created and its task is to provide consistency of man pages (and documentation in general). The results are now available for package maintainers to fix documentation issues.

If you need to re-run the check yourself, here is the simple process of man page check:

1. Download man-page-day from:

    https://pagure.io/ManualPageScan/blob/master/f/man-page-day.sh

2. Run the script:
    $ ./man-page-day.sh gfs2-utils

Comment 1 Maryna Nalbandian 2018-08-02 08:33:31 UTC
Created attachment 1472452 [details]
Logs

Comment 2 Jan Kurik 2018-08-14 10:47:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 3 Andrew Price 2019-10-15 14:32:19 UTC
The warnings don't look like issues to me and the only error in the log file has been fixed upstream in 6284d686590836ab2439a3c778559fa1188426aa


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