From: Xavier Delaruelle <xavier.delaruelle@gmail.com>
To: cygwin@cygwin.com
Subject: Missing 'sphinx-build' command from python37-sphinx package
Date: Sat, 8 Aug 2020 09:44:41 +0200 [thread overview]
Message-ID: <CAExoBLuHG2=Y5wMW0dJQD4zV1Jms29Qz_3kEQh8mbuD3s4NKEw@mail.gmail.com> (raw)
Hello,
I am using cygwin through the AppVeyor CI environment to check my software
build process and non-regression testsuite :
https://ci.appveyor.com/project/xdelaruelle/modules
In this environment I use python37-sphinx package to build the
documentation of the software, which requires the 'sphinx-build' command.
It seems that this 'sphinx-build' command has disappeared from
python37-sphinx package recently:
https://ci.appveyor.com/project/xdelaruelle/modules/builds/34537360/job/870u7prqtwgbwtnk
Which is confirmed by listing package content:
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fpython37-sphinx%2Fpython37-sphinx-3.1.2-1&grep=sphinx
This issue is also affecting the python36-sphinx package.
python38-package contains the 'sphinx-build' command, however it seems
there are some missing requirements to make this package operational. I get
an "Could not import extension sphinx.builders.epub3 (exception: No module
named 'sphinxcontrib')" error, see build log:
https://ci.appveyor.com/project/xdelaruelle/modules/builds/34542552/job/9tw241syk4upr4r1
Regards,
Xavier
next reply other threads:[~2020-08-08 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 7:44 Xavier Delaruelle [this message]
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
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='CAExoBLuHG2=Y5wMW0dJQD4zV1Jms29Qz_3kEQh8mbuD3s4NKEw@mail.gmail.com' \
--to=xavier.delaruelle@gmail.com \
--cc=cygwin@cygwin.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).