linux-kernel - Re: [PATCH 0/5] Make PDF builds work again

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: <20170618221829.4573592b@vento.lan>
Date:   Sun, 18 Jun 2017 22:18:29 -0300
From:   Mauro Carvalho Chehab <mchehab@...pensource.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Jim Davis <jim.epost@...il.com>,
        Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [PATCH 0/5] Make PDF builds work again

Hi Jon,

Em Sun, 18 Jun 2017 17:46:25 -0600
Jonathan Corbet <corbet@....net> escreveu:

> I've just spent rather more time than I would like figuring out why the PDF
> builds fail and what was needed to fix it.  The result is the following
> patch series.  It's a combination of little mistakes and fragility in the
> whole PDF build tool chain.

Yeah, the PDF toolchain is very fragile. Yet, I'm pretty sure I was able
to build PDF in the past without noticing the problems fixed by patches
1 and 2. Maybe the bugs has to do with some specific incompatibility with
toolchain versions.

What Sphinx version are you using?

It is too late now, but tomorrow I'll test with a few Spinx versions
and see if PDF builds equally well with them.

> 
> Mauro, Daniel: Do you want the last two?  Or otherwise give me acks?  I'd
> like to send the set Linusward forthwith so that 4.12 can come out with
> a working PDF build.

For the media and EDAC changes (patches 3 and 4), once I test it,
feel free to add my ack and send via your tree:

Acked-by: Mauro Carvalho Chehab <mchehab@...pensource.com>

> 
> In general, I'm dismayed by the fragility of the whole thing.  I'm also a
> little concerned that nobody except Jim complained about the problem.

Actually, despite any "errors", usually it produces the PDF files.
I have a robot building just the media documentation, daily basis,
from media development tree, at:
	https://linuxtv.org/downloads/v4l-dvb-apis-new/media.pdf

The robot is using Sphinx 1.4.8 version.
	
> Perhaps nobody really cares about PDF output anymore?  In the absence of a
> concerted effort on somebody's part, I predict that PDF building will be
> broken much of the time.  I have to wonder if it's worth it...
> 
> Jonathan Corbet (5):
>   Docs: Include the Latex "ifthen" package
>   Docs: Remove redundant geometry package inclusion
>   Docs: fix table problems in ras.rst
>   Docs: Use kernel-figure in vidioc-g-selection.rst
>   DRM: Fix an incorrectly formatted table
> 
>  Documentation/admin-guide/ras.rst                  | 10 ++--
>  Documentation/conf.py                              |  3 +-
>  .../media/uapi/v4l/vidioc-g-selection.rst          |  4 +-
>  include/drm/bridge/dw_hdmi.h                       | 70 +++++++++++-----------
>  4 files changed, 43 insertions(+), 44 deletions(-)
> 



Thanks,
Mauro