From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Sphinx version dependencies?
Date: Thu, 19 Jul 2018 12:04:00 -0700 [thread overview]
Message-ID: <20180719190400.GB4800@magnolia> (raw)
In-Reply-To: <20180719181556.GA21435@thunk.org>
On Thu, Jul 19, 2018 at 02:15:56PM -0400, Theodore Y. Ts'o wrote:
> Darrick has sent in patches to convert the ext4 documentation to use
> rst and to be built as part of the full kernel documentation thanks.
> In addition to that, he's imported the on-disk documentation from the
> ext4 wiki into the kernel sources, so hopefully we can keep it more up
> to date.
>
> When I was experimenting with this, I had to actually build the kernel
> docs using Sphinx for the first time. I'm using Debian testing, so at
> first I blindly followed the instructions by
> ./scripts/sphinx-pre-install:
>
> Detected OS: Debian GNU/Linux unstable (sid).
> /usr/local/bin/virtualenv sphinx_1.4
> . sphinx_1.4/bin/activate
> pip install -r Documentation/sphinx/requirements.txt
>
> But when I did that, Sphinx had heartburn over the ext4.rst file.
>
> ./include/linux/spi/spi.h:373: ERROR: Unexpected indentation.
> /usr/projects/linux/ext4/Documentation/filesystems/ext4/ext4.rst:139: ERROR: Malformed table.
> Column span alignment problem in table line 5.
Hmmm, apparently it's choking on the table heading borders not matching
the text:
====== ===========
Foo Bar
====== =========== <-- need to extend to EOL
Blah Blah blah blah blah
====== ===========
Though weirdly while I /can/ get this error to reproduce with the
virtualenv 1.4.9 release, I can't get it to reproduce with the 1.3.6 or
1.6.7 ubuntu packages. Maybe it's a python3 thing, maybe not? Seems
pretty fragile to me.
Anyway, I'll fix ext4.rst and resubmit that part to get this moving.
--D
> ...
>
> After consulting with Darrick, it appears the problem is that Sphinx8
> 1.4.9 was the problem. This is the version that
> Documentation/sphinx/requirements.txt calls for. He did his rst
> conversion work using Ubuntu 18.04's Sphinx 1.6.7.
>
> As it turns out Debian testing/unstable already has Sphinx 1.7.5 in
> its repository, so if I simply install Sphinx 1.7.5, it works fine.
> That's what I've done for now.
>
> So that leaves me with some questions:
>
> * Is there a reason why scripts/sphinx-pre-install suggested using a
> Python virtual environment and installing Sphinx 1.4.9 instead of
> using the distro's pre-packaged Sphinx for Debian unstable/testing?
>
> * Why does Documentation/sphinx/requirements.txt asking for such an
> old version of Sphinx?
>
> * Is it a requirement that *.rst files that are checked into the
> kernel repo have to work with Sphinx 1.4.9? Or is it sufficient
> that it works with Sphinx 1.6.7 and 1.7.5 (which are the prepackaged
> Debian and Ubuntu versions). And it looks like Fedora 28 has Sphinx
> 1.7.2 if I'm not mistaken. How many versions of Sphinx are various
> automated build/test systems using?
>
> Thanks,
>
> - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-19 19:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 18:15 Sphinx version dependencies? Theodore Y. Ts'o
2018-07-19 19:04 ` Darrick J. Wong [this message]
2018-07-20 7:30 ` Markus Heiser
2018-07-20 13:12 ` Theodore Y. Ts'o
2018-07-20 13:45 ` Markus Heiser
2018-07-20 14:52 ` Theodore Y. Ts'o
2018-07-20 16:00 ` Markus Heiser
2018-07-20 16:44 ` Darrick J. Wong
2018-07-20 16:58 ` Markus Heiser
2018-07-20 17:10 ` Darrick J. Wong
2018-07-20 20:43 ` Theodore Y. Ts'o
2018-07-20 21:28 ` Markus Heiser
2018-07-21 10:38 ` Jonathan Corbet
2018-07-20 15:04 ` Christoph Hellwig
2018-07-20 16:28 ` Markus Heiser
2018-07-20 17:08 ` Darrick J. Wong
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=20180719190400.GB4800@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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