linux-kernel - Re: [PATCH 00/11] Fix PDF doc builds on major distros

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: <142b209d-613a-4659-a0f7-27efa8c6be85@gmail.com>
Date: Tue, 19 Aug 2025 11:16:29 +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

Hi Mauro,

Please calm down.
Apologizes if my wording has annoyed you.

On Tue, 19 Aug 2025 03:02:39 +0200, Mauro Carvalho Chehab wrote:
> Em Tue, 19 Aug 2025 08:26:31 +0900
> Akira Yokosawa <akiyks@...il.com> escreveu:

[...]

>> Mauro, I can't review on 5/11 unless you provide me exact steps to reproduce
>> the font discovery issue you said you have observed under debian at 4/11 of
>> this series.  That is, without assuming your other series of build-wrapper.
> 
> See below.
> 
>> The build-wrapper should be upper compatible with the current way of
>> running sub-make, without any change in conf.py.
> 
> The build-wrapper series doesn't make any changes on conf.py:

Of course not, I'm well aware of the fact from the cover letter.

[...]

> 4. It prevents the usage of T1 fontenc fonts, which could be
>    caused by either one of those two reasons:
> 
> 	a) \sphinxhyphen{}
> 	b) index build
> 
> I got those when checking what packages were required on some
> distros (Debian, Ubuntu, Mageia, openMandriva, Gentoo).

I couldn't reproduce it at PATCH 4/11 under a Ubnutu-based container
I've been using, ignoring your sphinx-build-warpper series.

I'd really like to see the issue with my eyes on top current way of
doc building!

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.

I suspect you have encountered some issue due to some missing package/
setting in the container container side.

Or does the issue only appear when you run the script directly?

Of course, there always is a chance I might be missing something
important.

Regards,
Akira