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: <acc71988-4ed7-4df1-aa1f-a9d7a125ca53@gmail.com>
Date: Sun, 17 Aug 2025 18:46:35 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: 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

[-CC: bpf@...r]

On Sat, 16 Aug 2025 13:55:38 +0200, Mauro Carvalho Chehab wrote:
> Em Sat, 16 Aug 2025 14:06:43 +0900
> Akira Yokosawa <akiyks@...il.com> escreveu:
> 

[...]

> Works for me, but let's do it on a separate series. I still have more
> than 100 patches on my pile to be merged. This series is focused on
> making at least some PDFs to build where possible, addressing major
> problems at conf.py that are causing LaTeX to not work on several
> distros and to fix wrong package dependencies(*).
> 
> I'll add a TODO item on my queue to replace fom ImageMagick to
> Inkscape on a separate series.
> 
> (*) One of such problem you blamed sphinx-build-wrapper, but 
>     the issue is actually addressed on this series with fixes to conf.py: 
>     there are currently several troubles at latex_documents list and at
>     latex_elements.
> 
>     Those are causing wrong font detection on LaTeX.

I couldn't see what you are talking about at first, because there
have not been any such issues reported.

Also, after applying 1/11 ... 4/11 on top of current docs-next
(commit 0bbc2548ea85 ("Merge branch 'pre-install' into docs-mw"),
despite the changelog of 5/11 which claims to fix an issue under
debian, I couldn't reproduce the "! Corrupted NFSS tables" error
under Ubuntu 24.04 (noble).

I'm confused ...  How can I reproduce this?

It's getting really hard for me to keep up with your pace of changes
in doc build scripts, really.

Akira

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ