Message-ID: <20250820091530.068c4b62@foz.lan>
Date: Wed, 20 Aug 2025 09:15:30 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Akira Yokosawa <akiyks@...il.com>
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/11] Fix PDF doc builds on major distros

Em Wed, 20 Aug 2025 08:54:52 +0900
Akira Yokosawa <akiyks@...il.com> escreveu:

> 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@...il.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 think that inkscape x imagemagick/rsvg-convert itself has
anyhting to do with the problems I detected, as they're related to
font issues (still, I got an issue on one of my builds on kfigure
write file: encoding is missing at open, which may cause errors).

Yet, installing imagemagick + rsvg-convert might affect some other
packages that LaTeX would use.

> 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.

Just because you can't reproduce the issue, it doesn't mean it doesn't
exist. LaTeX builds are complex having it has lots of dependencies,
and may be affected by installed fonts, LC_* and LANG env vars, etc.

It should be noticed that a Docker container doesn't have the same
packages installed when compared with a LXC one.

-

IMO, instead of trying to reproduce the bug that was already fixed
by my patches, it would be a way more important if you can double
check if the changes introduce regressions.

I'm planning to submit a new version of this series, with this
patch split into 3 patches, with a better description, plus a
couple of other fixes. If you notice a regression caused by any
of the patches, please let us know, preferably pointing the the exact
patch that broke it. 

Thanks,
Mauro

Powered by blists - more mailing lists