qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aarushi Mehta <mehta.aaru20@gmail.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, jsnow@redhat.com
Subject: [Qemu-devel] [Bug] Docs build fails at interop.rst
Date: Mon, 20 May 2019 17:00:15 +0530	[thread overview]
Message-ID: <8c0a113e959cc2419aa52253c261e111ac9caf4a.camel@gmail.com> (raw)

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



             reply	other threads:[~2019-05-20 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 11:30 Aarushi Mehta [this message]
2019-05-20 16:37 ` [Qemu-devel] [Bug] Docs build fails at interop.rst John Snow
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=8c0a113e959cc2419aa52253c261e111ac9caf4a.camel@gmail.com \
    --to=mehta.aaru20@gmail.com \
    --cc=jsnow@redhat.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).