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 1612197 - Man page scan results for nfs-utils
Summary: Man page scan results for nfs-utils
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 29
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FedoraManpagescan
TreeView+ depends on / blocked
 
Reported: 2018-08-03 16:12 UTC by Maryna Nalbandian
Modified: 2019-11-13 18:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-13 18:59:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Logs (11.31 KB, text/plain)
2018-08-03 16:13 UTC, Maryna Nalbandian
no flags Details

Description Maryna Nalbandian 2018-08-03 16:12:53 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 nfs-utils

Comment 1 Maryna Nalbandian 2018-08-03 16:13:12 UTC
Created attachment 1473080 [details]
Logs

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

Comment 3 Ben Cotton 2019-10-31 20:49:36 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Steve Dickson 2019-11-13 18:59:05 UTC
Here are the errors:
[ Error ] binary /sbin/mount.nfs4 has no man page!
[ Error ] binary /sbin/umount.nfs4 has no man page!
No true there is a mount.nfs(8) name pages that talks about both binaries

[ Error ] binary /usr/sbin/nfsconvert has no man page!
This script is run once when rhel8 is installed to deprecated
/etc/sysconfig/nfs. Man page not needed. 

[ Error ] binary /usr/sbin/start-statd has no man page!
This used by mount.nfs to start rpc.statd(8). Man page is not needed. 

[ Error ] config file /etc/gssproxy/24-nfs-server.conf has no man page! Check it's content for proper documentation
This is documented in gssproxy.conf (5)

[ Error ] config file /etc/modprobe.d/lockd.conf has no man page! Check it's content for proper documentation
THis is self documented. 

[ Error ] config file /etc/request-key.d/id_resolver.conf has no man page! Check it's content for proper documentation
Documented in nfsidmap(5)


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