From: John Snow <jsnow@redhat.com>
To: Aarushi Mehta <mehta.aaru20@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug] Docs build fails at interop.rst
Date: Mon, 20 May 2019 12:37:46 -0400 [thread overview]
Message-ID: <81b5a062-2bb5-8b2f-6a33-1f886211fc09@redhat.com> (raw)
In-Reply-To: <8c0a113e959cc2419aa52253c261e111ac9caf4a.camel@gmail.com>
On 5/20/19 7:30 AM, Aarushi Mehta wrote:
> https://paste.fedoraproject.org/paste/kOPx4jhtUli---TmxSLrlw
> running python3-sphinx-2.0.1-1.fc31.noarch on Fedora release 31
> (Rawhide)
>
> uname - a
> Linux iouring 5.1.0-0.rc6.git3.1.fc31.x86_64 #1 SMP Thu Apr 25 14:25:32
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>
> Reverting commmit 90edef80a0852cf8a3d2668898ee40e8970e431
> allows for the build to occur
>
> Regards
> Aarushi Mehta
>
>
Ah, dang. The blocks aren't strictly conforming json, but the version I
tested this under didn't seem to care. Your version is much newer. (I
was using 1.7 as provided by Fedora 29.)
For now, try reverting 9e5b6cb87db66dfb606604fe6cf40e5ddf1ef0e7 instead,
which should at least turn off the "warnings as errors" option, but I
don't think that reverting -n will turn off this warning.
I'll try to get ahold of this newer version and see if I can't fix it
more appropriately.
--js
next prev parent reply other threads:[~2019-05-20 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 11:30 [Qemu-devel] [Bug] Docs build fails at interop.rst Aarushi Mehta
2019-05-20 16:37 ` John Snow [this message]
2019-05-20 21:25 ` [Qemu-devel] QMP Example Formatting in ReST, Sphinx, and Pygments (was: Re: [Bug] Docs build fails at interop.rst) John Snow
2019-05-20 23:04 ` Eduardo Habkost
2019-05-21 20:26 ` John Snow
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=81b5a062-2bb5-8b2f-6a33-1f886211fc09@redhat.com \
--to=jsnow@redhat.com \
--cc=mehta.aaru20@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).