From: Marco Atzeri <marco.atzeri@gmail.com>
To: Xavier Delaruelle <xavier.delaruelle@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Missing 'sphinx-build' command from python37-sphinx package
Date: Mon, 10 Aug 2020 10:11:07 +0200 [thread overview]
Message-ID: <5feee671-d580-5cdd-3d0f-06587690b108@gmail.com> (raw)
In-Reply-To: <9e1409df-2f7a-34b1-370c-cea9cc24406f@gmail.com>
On 10.08.2020 09:16, Marco Atzeri wrote:
> On 10.08.2020 06:58, Xavier Delaruelle wrote:
>> Hi Marco,
>>
>> I have been able to test new packages and now I am hitting another issue:
>>
>> Extension error:
>> Could not import extension sphinx.builders.epub3 (exception: No module
>> named 'sphinxcontrib.serializinghtml')
>>
>> The full log is available at [1].
>>
>> My software documentation does not rely on any extension (see [2]), so
>> I assume this is missing extension is something required when you want
>> to build the HTML documentation.
>>
>> My last build that went fine was 4 days ago. It used python37-sphinx
>> 1.8.5-1 (logs available at [3]).
>>
>> Regards,
>> Xavier
>>
>
> Hi Xavier,
> it seems some problem of how they modified the
> python-sphinx 3.1.2
>
> I hit the same problem than you on rebuilding cmake
> and I am building and adding new contrib packages
>
> python3x-sphinxcontrib-applehelp 1.0.2-1
> python3x-sphinxcontrib-devhelp 1.0.2-1
> python3x-sphinxcontrib-htmlhelp 1.0.3-1
> python3x-sphinxcontrib-serializinghtml 1.1.4-1
> python3x-sphinxcontrib-websupport 1.2.3-1
>
> I wonder if it is a side effect of not having yet ported
> python3x-sphinx-notfound-page
>
> as soon cmake documentation complete, I will upload all the
> new contrib packages
>
> Regards
> Marco
>
after adding also
python3x-sphinxcontrib-qthelp 1.0.3-1
I was able to build cmake documentation
let me know if you need any other sphinxcontrib-**
package
Regards
Marco
next prev parent reply other threads:[~2020-08-10 8:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 7:44 Xavier Delaruelle
2020-08-08 19:07 ` Marco Atzeri
2020-08-08 20:07 ` Hamish MB
2020-08-09 8:38 ` Xavier Delaruelle
2020-08-09 15:22 ` Marco Atzeri
2020-08-09 16:14 ` Xavier Delaruelle
2020-08-10 4:58 ` Xavier Delaruelle
2020-08-10 7:16 ` Marco Atzeri
2020-08-10 8:11 ` Marco Atzeri [this message]
2020-08-10 8:39 ` Xavier Delaruelle
2020-08-11 8:56 ` Xavier Delaruelle
2020-08-11 11:21 ` Marco Atzeri
2020-08-12 7:03 ` Marco Atzeri
2020-08-12 7:16 ` Xavier Delaruelle
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=5feee671-d580-5cdd-3d0f-06587690b108@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=xavier.delaruelle@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).