-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[warning] Unexpected final line in man document SYSTEMD-HWDB(8) #23184
Comments
This seems to be caused by That makes me wonder - why we skip the date part when generating systemd-related man pages? |
To make it reproducible?
…On Sun, 24 Apr 2022, 10:58 Frantisek Sumsal, ***@***.***> wrote:
This seems to be caused by yelp expecting the last line to be in a format
of <version> <date> <man_ref> and the systemd man pages don't have the
date part, see
https://gitlab.gnome.org/GNOME/yelp/-/blob/master/libyelp/yelp-man-parser.c#L1214-1222
.
That makes me wonder - why we skip the date part when generating
systemd-related man pages?
—
Reply to this email directly, view it on GitHub
<#23184 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEFFN66G2CAD2LNXO4XNY3VGUEKLANCNFSM5UF5PNQA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
That would certainly make sense, but it should be resolvable by using |
I do not know how this variable works... (I am not an expert of repro-builds...) |
I think the date at the bottom of the man pages is pretty useless. But if somebody preps a patch to insert $SOURCE_DATE_EPOCH there I'd be fine. Might make sense to make gnome's yelp deal with this natively however. |
I think it would be nicer if yelp would just be able to handle man pages like this. Hence I filed: |
This is a very low issue.
When I open man page of
systemd-hwdb
with GNOME's yelp,journalctl reports this:
NB: you can open the man document directly after
$ systemd-hwdb --help
or using direct command$ yelp "man:systemd-hwdb(8)"
The text was updated successfully, but these errors were encountered: