From: Akira Yokosawa <akiyks@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 00/11] Fix PDF doc builds on major distros
Date: Wed, 20 Aug 2025 08:54:52 +0900 [thread overview]
Message-ID: <08c3a7eb-0425-4709-a3ea-6d1d726fd3c8@gmail.com> (raw)
In-Reply-To: <20250819153200.3c2b2ff6@foz.lan>
On Tue, 19 Aug 2025 15:32:00 +0200, Mauro Carvalho Chehab wrote:
> Em Tue, 19 Aug 2025 11:16:29 +0900
> Akira Yokosawa <akiyks@gmail.com> escreveu:
[...]
>> That's all I am asking.
>>
>> I have no particular interest in the way you are testing all those
>> variety of distros, and have no idea about it.
>>
>> Please provide steps to reproduce.
>> I'd like to see a Dockerfile based "FROM ubuntu:latest" as the testing
>> environment.
>
> Heh, that's why you can't reproduce... you're using a Docker container
> and a different Ubuntu version than I.
>
> What I did here was to use a lxc container with 25.04, and used
> a script to pick the exact recommendations given by sphinx-pre-install.
>
> The container was created with:
>
[...]
> once you get what's needed for make htmldocs work, installing
> only the dependencies recommended by sphinx-pre-install, you can
> start trying to reproduce the build issues for pdf.
I've just built a container "FROM ubuntu:plucky", which has inkscape
instead of imagemagick + rsvg-convert.
I don't see any font issue at 4/11 of this series under the container
(I'm using podman).
Furthermore, after I applied both of your series and the change for
parallel runs of xelatex/latexmk and reverting the 5/11, I don't see
any issue.
Which strongly suggests 5/11 is not fixing any realistic issues.
FWIW, Dockerfile I'm using for building the container is derived from the
one I've been taking care of since 2021 as a LaTeX advisor to perfbook.
If you are interested, here is its repo of Paul:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/perfbook.git
You might be interested in seeing docker/Dockerfile.
I think there is something you are missing in the boot strapping phases
of building your container.
Just my wild guess.
Thanks,
Akira
next prev parent reply other threads:[~2025-08-19 23:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 11:36 Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 01/11] docs: Makefile: Fix LaTeX paper size settings Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 02/11] docs: conf.py: better handle latex documents Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 03/11] docs: conf.py: fix doc name with SPHINXDIRS Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 04/11] docs: conf.py: rename some vars at latex_documents logic Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 05/11] docs: conf.py: fix some troubles for LaTeX output Mauro Carvalho Chehab
2025-08-20 8:16 ` Akira Yokosawa
2025-10-02 16:30 ` ChaosEsque Team
2025-08-15 11:36 ` [PATCH 06/11] scripts: sphinx-pre-install: fix PDF build issues on Ubuntu Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 07/11] scripts: sphinx-pre-install: add missing gentoo pdf dependencies Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 08/11] scripts: sphinx-pre-install: fix PDF dependencies for openSuse Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 09/11] scripts: sphinx-pre-install: fix dependencies for OpenMandriva Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 10/11] scripts: sphinx-pre-install: fix pdf dependencies for Mageia 9 Mauro Carvalho Chehab
2025-08-15 11:36 ` [PATCH 11/11] scripts: sphinx-pre-install: fix PDF dependencies for gentoo Mauro Carvalho Chehab
2025-08-16 5:06 ` [PATCH 00/11] Fix PDF doc builds on major distros Akira Yokosawa
2025-08-16 11:55 ` Mauro Carvalho Chehab
2025-08-17 9:46 ` Akira Yokosawa
2025-08-17 11:36 ` Mauro Carvalho Chehab
2025-08-17 12:24 ` Akira Yokosawa
2025-08-17 13:45 ` Mauro Carvalho Chehab
2025-08-17 16:07 ` Akira Yokosawa
2025-08-18 0:44 ` Akira Yokosawa
2025-08-18 9:42 ` Mauro Carvalho Chehab
2025-08-18 10:06 ` Akira Yokosawa
2025-08-18 11:35 ` Mauro Carvalho Chehab
2025-08-18 12:00 ` Akira Yokosawa
2025-08-18 17:07 ` Jonathan Corbet
2025-08-18 23:26 ` Akira Yokosawa
2025-08-19 1:02 ` Mauro Carvalho Chehab
2025-08-19 2:16 ` Akira Yokosawa
2025-08-19 13:32 ` Mauro Carvalho Chehab
2025-08-19 23:54 ` Akira Yokosawa [this message]
2025-08-20 7:15 ` Mauro Carvalho Chehab
2025-08-20 11:41 ` Akira Yokosawa
2025-08-20 16:48 ` Mauro Carvalho Chehab
2025-08-20 23:53 ` Akira Yokosawa
2025-08-21 0:09 ` Akira Yokosawa
2025-08-21 7:52 ` Mauro Carvalho Chehab
2025-08-21 7:56 ` Mauro Carvalho Chehab
2025-08-21 9:12 ` Inkscape - Was: " Mauro Carvalho Chehab
2025-08-18 16:59 ` Jonathan Corbet
2025-08-17 15:32 ` Vegard Nossum
2025-08-18 8:33 ` Mauro Carvalho Chehab
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=08c3a7eb-0425-4709-a3ea-6d1d726fd3c8@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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
all inboxes | Powered by JetHome®