linux-kernel - Inkscape - Was: 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250821111205.15dc7843@foz.lan>
Date: Thu, 21 Aug 2025 11:12:05 +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: Inkscape - Was: Re: [PATCH 00/11] Fix PDF doc builds on major
 distros

Em Thu, 21 Aug 2025 09:09:41 +0900
Akira Yokosawa <akiyks@...il.com> escreveu:

> Hi,
> 
> Let me do a quick follow up.
> I messed up the table.
> 
> On Thu, 21 Aug 2025 08:53:04 +0900, Akira Yokosawa wrote:
> > Hi,
> > 
> > Commenting on your observation quoted below.
> > 
> > On Wed, 20 Aug 2025 18:48:10 +0200, Mauro Carvalho Chehab wrote:
> > [...]
> >   
> >> If you want a more comprehensive answer:
> >>
> >> LaTeX is highly dependent lots of packages, including fonts. The
> >> reason why you can't reproduce the font issues with Docker
> >> (I wasn't able to reproduce with Docker here as well) is
> >> probably due to either packaging differences between the
> >> two containers, due to different environment technologies
> >> or even due to the way Docker and LXC handles OS virtualization.
> >>  
> > 
> > I'm not saying there is no difference between Docker and LXC.
> > 
> > Can you fill in ???? cells in the table below ?  
> I mean                                          with this series applied
> 
> > Docker column is my observation of "FROM ubuntu:plucky" podman runs.
> > 
> >  "make SPHINXDIRS=gpu pdfdocs" under Ubuntu Plucky
> >   
> 
> I meant:
> 
>      --------------- --------- ----------
>      SVG --> PDF     Docker    LXC
>      --------------- --------- ----------
>      imagemagick     FAIL      ????
>      inkscape        SUCCESS   ????
>      imagemagick [*] FAIL      ????
>      --------------- --------- ----------
> 
> >     --------------- --------- ----------
> >     SVG --> PDF     Docker    LXC
> >     --------------- --------- ----------
> >     imagemagick     FAIL      FAIL
> >     inkscape        SUCCESS   ????
> >     imagemagick [*] FAIL      ????
> >     --------------- --------- ----------
> > 
> > [*] after installing both inkscape and imagemagick, remove inkscape
> >     with all its dependencies kept.
> > 
> > Do you see any difference between Docker and LXC columns in the table?
> > I'm all ears.

I'm repeating my tests again. This time, it has just this
series applied:

	https://lore.kernel.org/linux-doc/cover.1755763127.git.mchehab+huawei@kernel.org/T/#t

(without that, not even simple PDF docs build here via Sphinx on Ubuntu)


LXC container created from scratch, with a couple unrelated packages
to make life easier (things like ssh server) and with locale-gen
executed there.

After its creation, I copied the
relevant files from my machine to the container with:

	for ip in 10.0.3.129; do for d in Documentation scripts Makefile arch include tools; do rsync -av --times --delete "$d" "root@$ip:/root" --exclude output/; done; done

Then, at the container (accessed via ssh):

	# Sphinx pre-install recommendations
        sudo apt-get install dvipng fonts-noto-cjk graphviz imagemagick latexmk librsvg2-bin tex-gyre texlive-fonts-recommended texlive-lang-chinese texlive-xetex
        sudo apt-get install python3-sphinx

	# Needed to avoid sphinx-build crashes
	for i in $(set|grep LC|cut  -d'=' -f1); do unset $i;done
	export LC_ALL=C
	export LANG=C

with that:

imagemagick: FAIL
inkscape: PASS
imagemagick(*): FAIL

I wonder if this is related to the kfigure.py bug of writing
a binary output with a file opened in "w" mode. In Python,
"w" crashes for characters > 127. It should instead be "wb".

Thanks,
Mauro