-
-
Notifications
You must be signed in to change notification settings - Fork 390
Fix man page section assignments for end-user interactive clients #2977
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…gest_doc_links_CMD_USR() [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…scmd/upsrw [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…ments [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…gest_doc_links_CMD_USR() [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…scmd/upsrw [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
c19e07d
to
1c9a5d2
Compare
… clients (man1) [networkupstools#2977] * Section 1 (programs): upsc, upscmd, upsrw, NUT-Monitor * Section 8 (daemons): upsmon, upssched Signed-off-by: Jim Klimov <[email protected]>
…gest_doc_links_CMD_USR() [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…scmd/upsrw [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…tworkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
… clients (man1) [networkupstools#2977] * Section 1 (programs): upsc, upscmd, upsrw, NUT-Monitor * Section 8 (daemons): upsmon, upssched Signed-off-by: Jim Klimov <[email protected]>
…gest_doc_links_CMD_USR() [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…scmd/upsrw [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…tworkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
Due to the questionable nature of the man page section change, this PR was split: #2978 takes care of general docs improvements (including the fix of man sections from Raised a discussion on mailing list: https://alioth-lists.debian.net/pipermail/nut-upsdev/2025-June/008151.html |
❌ Build nut 2.8.3.3258-master failed (commit aa2d795a1c by @jimklimov) |
… clients (man1) [networkupstools#2977] * Section 1 (programs): upsc, upscmd, upsrw, NUT-Monitor * Section 8 (daemons): upsmon, upssched Signed-off-by: Jim Klimov <[email protected]>
…gest_doc_links_CMD_USR() [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…scmd/upsrw [networkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
…tworkupstools#2977] Signed-off-by: Jim Klimov <[email protected]>
Rebased over recent state of PR #2978 as it got merged. |
❌ Build nut 2.8.3.3264-master failed (commit ca7a491e62 by @jimklimov) |
For now suspending this idea, maybe even until after a NUT v2.8.4 release. May lead to path re-assignments for some programs as well. |
There was some mess in existing pages; bolt down the man pave section for these programs:
upsc
,upscmd
,upsrw
andNUT-Monitor
. Being (semi-)interactive end-user clients, they belong in section 1 rather than 8 (system daemons)..html
extension).UPDATE: Due to the questionable nature of the man page section change, this PR was split: #2978 takes care of general docs improvements (including the fix of man sections from
1
to8
where they got mis-referenced in existing docs vs. existing layout), and this PR was rebased on top of that to propose the re-organization of the layout itself. Also, should this go further, moving tools likenut-scanner
andnutconf
to section 1? If we do end up breaking everyone's packaging recipes, better limit the pain to one NUT release.Raised a discussion on mailing list: https://alioth-lists.debian.net/pipermail/nut-upsdev/2025-June/008151.html