From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Sphinx version dependencies?
Date: Fri, 20 Jul 2018 10:10:20 -0700 [thread overview]
Message-ID: <20180720171020.GI4800@magnolia> (raw)
In-Reply-To: <93aa59853a491a5ba3d5c3bcc0c991a1b815a67d.camel@darmarit.de>
On Fri, Jul 20, 2018 at 06:58:57PM +0200, Markus Heiser wrote:
> Am Freitag, den 20.07.2018, 09:44 -0700 schrieb Darrick J. Wong:
> > and now I'm just confused since 16.04 has the same version of docutils
> > and an older sphinx and runs fine; but 18.04 has newer docutils and
> > newer sphinx and runs fine.
>
> Same here .. I'am completely confused by distros etc. .. I will never be able to
> control that. Thats why I recommend the virtualenv workflow (as I wrote Christoph):
Well yes, but it's the virtualenv workflow that produced build errors
for Ted; that's what would seem to need fixing?
--D
> $ sudo apt install python3-virtualenv
>
> To setup up a environment for building htmldocs:
>
> $ python3 -m virtualenv py3env
> $ ./py3env/bin/pip install -r ./Documentation/sphinx/requirements.txt
>
> To build htmldocs with:
>
> $ SPHINXBUILD=./py3env/bin/sphinx-build make htmldocs
>
> If the env is no longer needed:
>
> $ rm -r py3env
>
> Am Freitag, den 20.07.2018, 09:44 -0700 schrieb Darrick J. Wong:
> > Yes. This makes writing broadly portable markup difficult -- originally
> > I did not take the '=' all the way to the right edge of the table
> > because I saw that last example in the above document and assumed that
> > it wasn't necessary to extend the '=' all the way to the right edge.
> > Neither Ubuntu system choked on it, so is this a bug in upstream? Some
> > strange patch added by the distro? Something that ended up in the
> > python wheel? Or a bug in the spec?
>
> I guess in the version history of docutils ;) .. use workflow above to escape
> from distro chaos. Even missing '=' will be OK.
>
> -- Markus --
WARNING: multiple messages have this Message-ID (diff)
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Sphinx version dependencies?
Date: Fri, 20 Jul 2018 10:10:20 -0700 [thread overview]
Message-ID: <20180720171020.GI4800@magnolia> (raw)
In-Reply-To: <93aa59853a491a5ba3d5c3bcc0c991a1b815a67d.camel@darmarit.de>
On Fri, Jul 20, 2018 at 06:58:57PM +0200, Markus Heiser wrote:
> Am Freitag, den 20.07.2018, 09:44 -0700 schrieb Darrick J. Wong:
> > and now I'm just confused since 16.04 has the same version of docutils
> > and an older sphinx and runs fine; but 18.04 has newer docutils and
> > newer sphinx and runs fine.
>
> Same here .. I'am completely confused by distros etc. .. I will never be able to
> control that. Thats why I recommend the virtualenv workflow (as I wrote Christoph):
Well yes, but it's the virtualenv workflow that produced build errors
for Ted; that's what would seem to need fixing?
--D
> $ sudo apt install python3-virtualenv
>
> To setup up a environment for building htmldocs:
>
> $ python3 -m virtualenv py3env
> $ ./py3env/bin/pip install -r ./Documentation/sphinx/requirements.txt
>
> To build htmldocs with:
>
> $ SPHINXBUILD=./py3env/bin/sphinx-build make htmldocs
>
> If the env is no longer needed:
>
> $ rm -r py3env
>
> Am Freitag, den 20.07.2018, 09:44 -0700 schrieb Darrick J. Wong:
> > Yes. This makes writing broadly portable markup difficult -- originally
> > I did not take the '=' all the way to the right edge of the table
> > because I saw that last example in the above document and assumed that
> > it wasn't necessary to extend the '=' all the way to the right edge.
> > Neither Ubuntu system choked on it, so is this a bug in upstream? Some
> > strange patch added by the distro? Something that ended up in the
> > python wheel? Or a bug in the spec?
>
> I guess in the version history of docutils ;) .. use workflow above to escape
> from distro chaos. Even missing '=' will be OK.
>
> -- Markus --
--
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-20 17:10 UTC|newest]
Thread overview: 31+ 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
2018-07-20 7:30 ` Markus Heiser
2018-07-20 7:30 ` Markus Heiser
2018-07-20 13:12 ` Theodore Y. Ts'o
2018-07-20 13:12 ` Theodore Y. Ts'o
2018-07-20 13:45 ` Markus Heiser
2018-07-20 13:45 ` Markus Heiser
2018-07-20 14:52 ` Theodore Y. Ts'o
2018-07-20 14:52 ` Theodore Y. Ts'o
2018-07-20 16:00 ` Markus Heiser
2018-07-20 16:00 ` Markus Heiser
2018-07-20 16:44 ` Darrick J. Wong
2018-07-20 16:44 ` Darrick J. Wong
2018-07-20 16:58 ` Markus Heiser
2018-07-20 16:58 ` Markus Heiser
2018-07-20 17:10 ` Darrick J. Wong [this message]
2018-07-20 17:10 ` Darrick J. Wong
2018-07-20 20:43 ` Theodore Y. Ts'o
2018-07-20 20:43 ` Theodore Y. Ts'o
2018-07-20 21:28 ` Markus Heiser
2018-07-20 21:28 ` Markus Heiser
2018-07-21 10:38 ` Jonathan Corbet
2018-07-21 10:38 ` Jonathan Corbet
2018-07-20 15:04 ` Christoph Hellwig
2018-07-20 15:04 ` Christoph Hellwig
2018-07-20 16:28 ` Markus Heiser
2018-07-20 16:28 ` Markus Heiser
2018-07-20 17:08 ` Darrick J. Wong
2018-07-20 17:08 ` Darrick J. Wong
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=20180720171020.GI4800@magnolia \
--to=darrick.wong@oracle.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--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 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.