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: <16b48826-6634-4ec9-86a0-7ddb59ce3bed@gmail.com>
Date: Tue, 19 Aug 2025 08:26:31 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Jonathan Corbet <corbet@....net>,
 Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: 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 Mon, 18 Aug 2025 11:07:58 -0600, Jonathan Corbet wrote:
> Akira Yokosawa <akiyks@...il.com> writes:
> 
>> Ah, I have finally understood what 5/11 is trying to do.
>>
>> Its changelog mainly talks about an issue you saw after adding options
>> to xindy in that same commit, and you added
>>
>>    \newfontfamily\headingfont{DejaVu Serif}
>>
>> to resolve it.
>>
>> Current changelog didn't make sense at all for me.
>>
>> Can you please reword it and make it easier to follow?
>>
>> With that, feel free to add my
>>
>> Reviewed-by: Akira Yokosawa <akiyks@...il.com>
> 
> So, if I have managed to understand this conversation, this reword is
> all we need to get this series merged..?

Well, after some thoughts on the conversation took place on xindy,
I think I have to withdraw my Reviewed-by: tag.

I was the one who was totally confused.

Please disregard it.

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.

The build-wrapper should be upper compatible with the current way of
running sub-make, without any change in conf.py.

I don't think this is too much to ask.  Moving both the goal post
and the build script at the same time is the wrong thing to do
in my opinion.

Regards,
Akira