From: Jonathan Corbet <corbet@lwn.net>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Jani Nikula <jani.nikula@intel.com>,
linux-doc@vger.kernel.org, Takashi Iwai <tiwai@suse.de>
Subject: Re: kernel-doc unbuildable with sphinx 1.7
Date: Fri, 2 Mar 2018 07:34:09 -0700 [thread overview]
Message-ID: <20180302073409.2cce15ff@lwn.net> (raw)
In-Reply-To: <1b24cf1c-941b-9f0d-21e5-b595f64c49b6@suse.cz>
On Fri, 2 Mar 2018 15:10:14 +0100
Jiri Slaby <jslaby@suse.cz> wrote:
> in openSUSE, sphinx was updated to 1.7.1 and kernel-doc cannot be built
> since that time:
> Running Sphinx v1.7.1
>
> Extension error:
> Could not import extension kerneldoc (exception: cannot import name
> 'Directive')
>
> It is because sphinx.util.compat.* was removed from sphinx in 1.7 since
> it was deprecated for a long time:
> "sphinx.util.compat.%s is deprecated and will be removed "
> "in Sphinx 1.7, please use docutils' instead."
>
>
> Could you fix that up? python is not my favourite interpreter so fixing
> it myself is not feasible on my side.
I got a patch from Takashi this very morning for that problem; I guess
I'll have to fast-track it Linusward.
Thanks,
jon
--
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-03-02 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 14:10 kernel-doc unbuildable with sphinx 1.7 Jiri Slaby
2018-03-02 14:34 ` Jonathan Corbet [this message]
2018-03-02 14:40 ` Jiri Slaby
2018-03-02 14:44 ` Takashi Iwai
2018-03-02 14:52 ` Jonathan Corbet
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=20180302073409.2cce15ff@lwn.net \
--to=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=jslaby@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=tiwai@suse.de \
/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.