From: Akira Yokosawa <akiyks@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, mchehab@kernel.org
Subject: Re: make pdfdocs fails on Debian stable
Date: Tue, 4 Jan 2022 22:46:57 +0900 [thread overview]
Message-ID: <2fb003aa-545c-31a4-1466-8c3c3fc708fb@gmail.com> (raw)
In-Reply-To: <20220104131952.GA21933@lst.de>
On Tue, 4 Jan 2022 14:19:52 +0100, Christoph Hellwig wrote:
> On Tue, Jan 04, 2022 at 06:31:01PM +0900, Akira Yokosawa wrote:
>> Hi, getting back to the error message, I remember seeing a similar error
>> when I failed to permit PDF output of ImageMagick.
>>
>> What I did back then was this (as root):
>>
>> # cd /etc/ImageMagick-6
>> # sed -i 's+policy domain="coder" rights="none" pattern="PDF"+policy domain="coder" rights="read|write" pattern="PDF"+' policy.xml ; \
>>
>> In case this resolves your issue.
>
> I've definitively seen permission denied errors earlier in the (rather
> noisy) build log. But I absolutely do not feel comfortable changing
> global security policies for a kernel build, especially for something
> like ImageMagic that had its fair share of security issues. Is there any
> way to side step this by using a different tool?
>
See my pending patch set at:
https://lore.kernel.org/linux-doc/e01fe9f9-f600-c2fc-c6b3-ef6395655ffe@gmail.com
[PATCH v2 0/4] docs: sphinx/kfigure.py: Improve conversion to PDF
This uses Inkscape if it is available instead of ImageMagick.
No imagemagick nor librsvg2-bin is required.
As long as if you can trust Inkscape...
Good luck!
Thanks, Akira
next prev parent reply other threads:[~2022-01-04 13:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:30 Christoph Hellwig
2022-01-03 16:58 ` Mauro Carvalho Chehab
2022-01-03 17:11 ` Christoph Hellwig
2022-01-03 20:58 ` Mauro Carvalho Chehab
2022-01-03 21:01 ` [PATCH 0/1] Detect the need of texlive-ctex Mauro Carvalho Chehab
2022-01-03 21:01 ` [PATCH 1/1] scripts: sphinx-pre-install: add required ctex dependency Mauro Carvalho Chehab
2022-01-03 22:46 ` Jonathan Corbet
2022-01-04 0:04 ` Akira Yokosawa
2022-01-04 1:54 ` Akira Yokosawa
2022-01-04 8:05 ` Mauro Carvalho Chehab
2022-01-04 10:26 ` Akira Yokosawa
2022-01-05 7:48 ` Mauro Carvalho Chehab
2022-01-05 12:09 ` Akira Yokosawa
2022-01-05 21:42 ` Mauro Carvalho Chehab
2022-01-05 22:57 ` Akira Yokosawa
2022-01-06 0:41 ` [PATCH v2] scripts: sphinx-pre-install: Fix ctex support on Debian Mauro Carvalho Chehab
2022-01-06 2:00 ` Akira Yokosawa
2022-01-06 22:35 ` Jonathan Corbet
2022-01-06 0:42 ` [PATCH 1/1] scripts: sphinx-pre-install: add required ctex dependency Mauro Carvalho Chehab
2022-01-04 2:00 ` Akira Yokosawa
2022-01-04 6:47 ` make pdfdocs fails on Debian stable Christoph Hellwig
2022-01-04 7:32 ` Akira Yokosawa
2022-01-04 7:36 ` Christoph Hellwig
2022-01-04 7:53 ` Akira Yokosawa
2022-01-04 7:56 ` Christoph Hellwig
2022-01-04 8:07 ` Akira Yokosawa
2022-01-04 8:16 ` Christoph Hellwig
2022-01-04 8:44 ` Akira Yokosawa
2022-01-04 9:31 ` Akira Yokosawa
2022-01-04 13:19 ` Christoph Hellwig
2022-01-04 13:46 ` Akira Yokosawa [this message]
2022-01-05 1:47 ` Akira Yokosawa
2022-01-05 7:35 ` Christoph Hellwig
2022-01-05 12:03 ` Akira Yokosawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2fb003aa-545c-31a4-1466-8c3c3fc708fb@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome