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: <20250821095221.5e6510f5@foz.lan>
Date: Thu, 21 Aug 2025 09:52:21 +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: 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      ????
>      --------------- --------- ----------

This is after my series, with doesn't deal with imagemagick/inkscape,
it only fixes broken texlive dependencies and fix font handling:

# (dpkg -l |grep -i magick; dpkg -l |grep inkscape)|grep ii
ii  imagemagick                   8:7.1.1.43+dfsg1-1                    amd64        image manipulation programs -- binaries
ii  imagemagick-7-common          8:7.1.1.43+dfsg1-1                    all          image manipulation programs -- infrastructure
ii  imagemagick-7.q16             8:7.1.1.43+dfsg1-1                    amd64        image manipulation programs -- quantum depth Q16
ii  libmagickcore-7.q16-10:amd64  8:7.1.1.43+dfsg1-1                    amd64        low-level image manipulation library -- quantum depth Q16
ii  libmagickwand-7.q16-10:amd64  8:7.1.1.43+dfsg1-1                    amd64        image manipulation library -- quantum depth Q16

# make SPHINXDIRS=gpu pdfdocs

Summary
=======
gpu: gpu/pdf/gpu.pdf

All PDF files were built.

# rm -rf Documentation/output/gpu/*
# (dpkg -l |grep -i magick; dpkg -l |grep inkscape)|grep ii
ii  imagemagick                     8:7.1.1.43+dfsg1-1                    amd64        image manipulation programs -- binaries
ii  imagemagick-7-common            8:7.1.1.43+dfsg1-1                    all          image manipulation programs -- infrastructure
ii  imagemagick-7.q16               8:7.1.1.43+dfsg1-1                    amd64        image manipulation programs -- quantum depth Q16
ii  libimage-magick-perl            8:7.1.1.43+dfsg1-1                    all          Perl interface to the ImageMagick graphics routines
ii  libimage-magick-q16-perl        8:7.1.1.43+dfsg1-1                    amd64        Perl interface to the ImageMagick graphics routines -- Q16 version
ii  libmagickcore-7.q16-10:amd64    8:7.1.1.43+dfsg1-1                    amd64        low-level image manipulation library -- quantum depth Q16
ii  libmagickwand-7.q16-10:amd64    8:7.1.1.43+dfsg1-1                    amd64        image manipulation library -- quantum depth Q16
ii  inkscape                   

# rm -rf Documentation/output/gpu/*
# (dpkg -l |grep -i magick; dpkg -l |grep inkscape)|grep ii
ii  inkscape                        1.2.2-8build1                         amd64        vector-based drawing program

# make SPHINXDIRS=gpu pdfdocs

Summary
=======
gpu: gpu/pdf/gpu.pdf

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

Yes. After having texlive dependencies fixed, and addressing the broken
conf.py file that is not aligned with modern Sphinx practices, it passed
on all three scenarios.

Please notice that addressing image was not the intent of this series.

The goal was *just* to fix texlive dependencies and fix text font
mapping that were causing troubles on Ubuntu and on other distros.


Thanks,
Mauro

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ