All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Christoph Hellwig <hch@lst.de>
Subject: [PATCH 0/1] Detect the need of texlive-ctex
Date: Mon,  3 Jan 2022 22:01:56 +0100	[thread overview]
Message-ID: <cover.1641243581.git.mchehab@kernel.org> (raw)
In-Reply-To: <20220103215831.2e65bb94@coco.lan>

Hi Jon,

Based on Christoph's report, it seems we need to add an extra dependency
for PDF builds.

Mauro Carvalho Chehab (1):
  scripts: sphinx-pre-install: add required ctex dependency

 scripts/sphinx-pre-install | 1 +
 1 file changed, 1 insertion(+)

-- 
2.33.1



  reply	other threads:[~2022-01-03 21:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 16:30 make pdfdocs fails on Debian stable 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       ` Mauro Carvalho Chehab [this message]
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
     [not found]                                 ` <20220106043707.0d40cd11@coco.lan>
2022-01-09  4:09                                   ` Akira Yokosawa
2022-01-09  6:28                                     ` Mauro Carvalho Chehab
2022-01-09  7:48                                       ` 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
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=cover.1641243581.git.mchehab@kernel.org \
    --to=mchehab@kernel.org \
    --cc=corbet@lwn.net \
    --cc=hch@lst.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.