FS#48369 - [systemd] missing man pages for systemd-journal-upload and others

Attached to Project: Arch Linux
Opened by Christian Rebischke (Shibumi) - Sunday, 28 February 2016, 16:02 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 28 February 2016, 18:16 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Hello,
There are man pages missing in the current systemd version 229-3 for systemd-journal-upload, systemd-journal-remote and other binaries in /usr/lib/systemd also some of these binaries are not linked or moved to /usr/bin/.

best regards

chris
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 28 February 2016, 18:16 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Nothing to do here
Comment by Doug Newgard (Scimmia) - Sunday, 28 February 2016, 16:43 GMT
They aren't missing:
usr/share/man/man8/systemd-journal-remote.8.gz
usr/share/man/man8/systemd-journal-upload.8.gz

Why would the binaries be symlinked or moved to /usr/bin when they're not meant to be run directly?
Comment by Dave Reisner (falconindy) - Sunday, 28 February 2016, 18:15 GMT
Upstream's rationale for putting a binary in /usr/bin is that it's useful when run directly and generally considered to be stable. Recent examples of binaries moving from /usr/lib are systemd-resolve and systemd-activate. Binaries like systemd-journald-remote and systemd-journald-upload are meant to be run via their respective services, and therefore will never be moved out of /usr/lib.

I've no idea how you managed to install systemd without these manpages, but they're assuredly present in the tarball.

There's no bug here, so... closing.

Loading...