Linux Manual Pages development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 221715] New: “make -R build-pdf-pages-troff” fails with “warning: table row does not fit”
Date: Fri, 03 Jul 2026 00:13:12 +0000	[thread overview]
Message-ID: <bug-221715-11311@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221715

            Bug ID: 221715
           Summary: “make -R build-pdf-pages-troff” fails with “warning:
                    table row does not fit”
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: man-pages
          Assignee: documentation_man-pages@kernel-bugs.osdl.org
          Reporter: jason@jasonyundt.email
        Regression: No

Created attachment 310413
  --> https://bugzilla.kernel.org/attachment.cgi?id=310413&action=edit
A full log of what happens when I follow the steps to reproduce on my system

Steps to reproduce:

1. Open a terminal.

2. Make sure that you have a copy of the man-pages repository on your system.

3. Change directory into the root of the repository by running this command:

        cd <path to repository>

4. (Optional) Make sure that you’re using the same set of dependencies that I
   used when I tried building man-pages by doing the following:

        A. Make sure that the Nix package manager is installed by running this
           command:

                nix-env --version

           If that command finishes successfully, then Nix is installed. If
           that command gives you an error, then you need to install Nix.

        B. Activate a dev shell that contains all of the dependencies for
           building man-pages by running this command:

                nix --extra-experimental-features 'nix-command flakes' develop
'git+https://codeberg.org/JasonYundt/flake-for-working-on-man-pages.git?ref=refs/heads/main&rev=d3e76acfbb2f036aa9215e930b624f80813b7f3e'

5. (Optional) Switch to a revision of man-pages that is known to have this
problem by running this command:

        git switch --detach a12be0058be628f50da69fb0efb2ed9b4422a699

6. Attempt to build the “build-pdf-pages-troff” target by running this command:

        make -R build-pdf-pages-troff


When I follow those steps to reproduce on my system, the build fails with these
errors:

> .tmp/man/man4/console_codes.4:420: warning: table row does not fit on page 5
> .tmp/man/man4/console_codes.4:778: warning: table row does not fit on page 9
> make: ***
> [/home/jayman/Documents/Home/VC/space_afraid/Git/partially_mine/man-pages/Repo/share/mk/build/pdf/pages/troff.mk:30:
> .tmp/man/man4/console_codes.4.pdf.set] Error 1
> make: *** Deleting file '.tmp/man/man4/console_codes.4.pdf.set'

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2026-07-03  0:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  0:13 bugzilla-daemon [this message]
2026-07-03 10:50 ` [Bug 221715] “make -R build-pdf-pages-troff” fails with “warning: table row does not fit” bugzilla-daemon

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=bug-221715-11311@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox