Bug 250332 - zfs(8) manpage subcommand lines missing
Summary: zfs(8) manpage subcommand lines missing
Status: Closed DUPLICATE of bug 237514
Alias: None
Product: Documentation
Classification: Unclassified
Component: Manual Pages (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs (Nobody)
URL: https://www.freebsd.org/cgi/man.cgi?q...
Keywords:
Depends on: 237514
Blocks:
  Show dependency treegraph
 
Reported: 2020-10-14 07:59 UTC by ivanngeow
Modified: 2024-04-15 13:16 UTC (History)
4 users (show)

See Also:
ivanngeow: maintainer-feedback-


Attachments
missing subcommand lines (44.75 KB, image/png)
2020-10-14 07:59 UTC, ivanngeow
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description ivanngeow 2020-10-14 07:59:45 UTC
Created attachment 218731 [details]
missing subcommand lines

On the Subcommands section of the zfs(8) manpage, a subcommand is listed followed by the description of what it does, and its options.

When rendered on the FreeBSD manpage site, the line that states the subcommand (eg 'zfs create [-pu] [-o property=value]... filesystem') is missing.

This problem is seen across all display formats rendered by the site: html, ascii, pdf. It has been reproduced using the Micro$oft Edge (screenshot attached) and Firefox browsers.

This problem occurs when viewing the 12.1-RELEASE and 11.4-RELEASE versions of the manpage.

eg https://www.freebsd.org/cgi/man.cgi?query=zfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html

This problem is NOT seen when viewing the 10.4-RELEASE version of the manpage.

https://www.freebsd.org/cgi/man.cgi?query=zfs&apropos=0&sektion=0&manpath=FreeBSD+10.4-RELEASE&arch=default&format=html

IMPACT:
The manpage is essentially useless for its purpose of being a reference for the subcommands, if the subcommand it is describing is missing. The impact is HIGH.
Comment 1 Wolfram Schneider freebsd_committer freebsd_triage 2020-10-14 15:11:04 UTC
I think this is a duplicate of #237514

It was fixed in 13-current, but apparently not back ported to 11.3 and 12 series
Comment 2 Wolfram Schneider freebsd_committer freebsd_triage 2024-04-15 13:16:50 UTC

*** This bug has been marked as a duplicate of bug 237514 ***