emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#52909: closed (Some man pages are not built correctly)


From: GNU bug Tracking System
Subject: bug#52909: closed (Some man pages are not built correctly)
Date: Tue, 27 Sep 2022 20:26:02 +0000

Your message dated Tue, 27 Sep 2022 16:25:16 -0400
with message-id <87bkr0y383.fsf@gmail.com>
and subject line Re: bug#52909: Some man pages are not built correctly
has caused the debbugs.gnu.org bug report #52909,
regarding Some man pages are not built correctly
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
52909: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52909
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Some man pages are not built correctly Date: Thu, 30 Dec 2021 19:00:45 -0500
On Guix Git commit c7d74a9bccfc1b1274fc8754a6e78bb6887c7fea, at least
some manpages are not being built correctly for packages such as elogind
and gnome-keyring-daemon. Are we seeing raw groff input? I'm not sure of
the technology used here.



--- End Message ---
--- Begin Message --- Subject: Re: bug#52909: Some man pages are not built correctly Date: Tue, 27 Sep 2022 16:25:16 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hi Leo,
>
> Leo Famulari <leo@famulari.name> writes:
>
>> On Guix Git commit c7d74a9bccfc1b1274fc8754a6e78bb6887c7fea, at least
>> some manpages are not being built correctly for packages such as elogind
>> and gnome-keyring-daemon. Are we seeing raw groff input? I'm not sure of
>> the technology used here.

[...]

> I've read the same kind of issue reported to the bind9
> project and its resolution, which was very helpful:
> https://gitlab.isc.org/isc-projects/bind9/-/issues/2310.  It seems it's
> a DocBook XSL stylesheet problem resolved in
> https://github.com/docbook/xslt10-stylesheets/pull/111 but not yet
> released...

This is now fixable in an ad-hoc fashion on master by replacing the
problematic docbook-xsl with docbook-xsl-next, and fixed for good on
core-updates.

Closing.

Thanks,

Maxim


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]