lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08c3a7eb-0425-4709-a3ea-6d1d726fd3c8@gmail.com>
Date: Wed, 20 Aug 2025 08:54:52 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH 00/11] Fix PDF doc builds on major distros

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ