From: Alejandro Colomar <alx@kernel.org>
To: Hugo Buddelmeijer <hugo@buddelmeijer.nl>
Cc: linux-man@vger.kernel.org, g.branden.robinson@gmail.com
Subject: Re: `make -R check` fails due to futex_waitv.2 and console_codes.4 being too wide
Date: Mon, 19 Oct 2026 08:20:29 +0200 [thread overview]
Message-ID: <atW2F1hvJPm2WV5y@debian> (raw)
In-Reply-To: <448efb68-e2ff-41d8-a575-97da30e293ff@buddelmeijer.nl>
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
Hi Hugo,
> Date: 2026-10-17 21:19:22+0200
> From: Hugo Buddelmeijer <hugo@buddelmeijer.nl>
>
> Hi Alejandro,
>
> Running `make -R check` fails because the text in futex_waitv.2 and
> console_codes.4 is too wide.
>
> I noticed this when trying to enable the test phase when updating the
> man-pages package in Guix; see https://codeberg.org/guix/guix/pulls/11893
Thanks a lot for the report. I'm very interested in having make check
pass cleanly.
> That Guix pull request contains a patch to fix the man-pages so `make check`
> passes; said patch is attached.
Thanks!
>
> Maybe you could device a better patch though, in particular for
> console_codes. The affected table is much narrower than similar tables, so
> some lines that have to be truncated, would easily fit in one of the other
> tables. But I couldn't easily figure out what determines the column widths,
> so I didn't fix that.
I think Branden might be better at that; I've added him to CC.
> Also, the Changelog for 6.04 contains some instructions to touch certain
> files to ensure the test suite passes. I did not attempt to use that
> workaround.
Ok.
> Thanks for maintaining these man pages, they contain such a wealth of
> information.
Thanks! :-)
> No need to credit me in case you fix these minor things.
I will, anyway. ;)
>
> Hugo
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-10-19 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 19:19 `make -R check` fails due to futex_waitv.2 and console_codes.4 being too wide Hugo Buddelmeijer
2026-10-19 6:20 ` Alejandro Colomar [this message]
2026-10-19 13:02 ` table layout in console_codes.4 (was: `make -R check` fails due to futex_waitv.2 and console_codes.4 being too wide) G. Branden Robinson
2026-10-19 16:55 ` Alejandro Colomar
2026-10-19 18:32 ` table layout in console_codes.4 Hugo Buddelmeijer
2026-10-19 22:41 ` table layout in console_codes.4 (was: `make -R check` fails due to futex_waitv.2 and console_codes.4 being too wide) G. Branden Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=atW2F1hvJPm2WV5y@debian \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=hugo@buddelmeijer.nl \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.