From: John Snow <jsnow@redhat.com>
To: Bruce Rogers <brogers@suse.com>,
peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Recent python-sphinx errors out building doc
Date: Wed, 19 Jun 2019 14:33:48 -0400 [thread overview]
Message-ID: <eb4dfc6a-563a-1f26-b566-cc6d640ab032@redhat.com> (raw)
In-Reply-To: <5a014061-224d-7fc9-313e-0a69a568c328@redhat.com>
On 6/19/19 2:15 PM, John Snow wrote:
>
>
> On 6/19/19 12:28 AM, Bruce Rogers wrote:
>>>>> On 6/18/2019 at 6:11 PM, John Snow <jsnow@redhat.com> wrote:
>>
>>>
>>> On 6/18/19 7:37 PM, Bruce Rogers wrote:
>>>> Hi,
>>>>
>>>> (Resent with correct address for John)
>>>> I build recent upstream qemu in the openSUSE Build Service, and for
>>>> the Factory repository there, python-sphinx was recently updated to
>>>> version 2.1.1. This caused the build to fail as follows:
>>>> /home/abuild/rpmbuild/BUILD/qemu-4.0.50/docs/interop/bitmaps.rst:202:Could
>>>> not lex literal_block as "json". Highlighting skipped.
>>>>
>>>> The python-sphinx tools is called with warnings are treated as errors
>>>> it looks like. I don't know much at all about this tool, and hopefully
>>>> someone knows what to fix here. If you want to give me a pointer
>>>> on what needs to change, I could give a go at doing a fix however.
>>>>
>>>> Thanks,
>>>>
>>>> Bruce
>>>
>>> Hi, there's a series designed to fix this:
>>>
>>> https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg00348.html
>>>
>>> I think it's up to Peter to merge it as the maintainer of the Sphinx
>>> machinery.
>>
>> Yup, this series fixes it for me. Thanks!
>>
>> Bruce
>>
>
> Correction: Peter already merged it. Sorry for the noise!
>
... Double correction, I misread the patch titles and it isn't merged.
Nobody should ever let me email before about 3-4PM EST, because my brain
isn't awake enough yet.
...Sorry for the noise 2x...
Peter, is the series ready for staging? I don't think the docs portion
needs any additional review beyond what it's already received.
--js
prev parent reply other threads:[~2019-06-19 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 22:49 [Qemu-devel] Recent python-sphinx errors out building doc Bruce Rogers
2019-06-18 23:37 ` Bruce Rogers
2019-06-19 0:11 ` John Snow
2019-06-19 4:28 ` Bruce Rogers
2019-06-19 18:15 ` John Snow
2019-06-19 18:33 ` John Snow [this message]
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=eb4dfc6a-563a-1f26-b566-cc6d640ab032@redhat.com \
--to=jsnow@redhat.com \
--cc=brogers@suse.com \
--cc=peter.maydell@linaro.org \
--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).