From: Xavier Delaruelle <xavier.delaruelle@gmail.com>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Missing 'sphinx-build' command from python37-sphinx package
Date: Mon, 10 Aug 2020 06:58:34 +0200 [thread overview]
Message-ID: <CAExoBLuBG+WeysC6O3ubenVSPtcW-9vBcvLR9RUTxP8P+Xj0Bw@mail.gmail.com> (raw)
In-Reply-To: <CAExoBLv_TkpaErqjE7OG1072Et98n7Zk9YLK465x3byCccB=3Q@mail.gmail.com>
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
[1]
https://ci.appveyor.com/project/xdelaruelle/modules/build/job/pjnscuqaaof9sxmn
[2] https://github.com/xdelaruelle/modules/blob/master/doc/source/conf.py
[3]
https://ci.appveyor.com/project/xdelaruelle/modules/builds/34510331/job/l9dwhpry900bgmwk
Le dim. 9 août 2020 à 18:14, Xavier Delaruelle <xavier.delaruelle@gmail.com>
a écrit :
> Hi Marco.
>
> Thanks a lot for your work on this issue.
>
> Regards,
> Xavier
>
> Le dim. 9 août 2020 à 17:22, Marco Atzeri <marco.atzeri@gmail.com> a
> écrit :
>
>> On 09.08.2020 10:38, Xavier Delaruelle wrote:
>> > If command names are versioned it is important to get a consistent way
>> > for users to install THE package that provides the 'sphinx-build'
>> > command (the one without version reference in the name). Without having
>> > to search which specific package provides this command and without
>> > having to update this package reference when a new minor version of
>> > Python is added.
>> >
>> > Xavier
>> >
>>
>> Hi Xavier,
>>
>> next upload will use "alternatives" to provide the simlinks
>> so depending which version you install the default version is the
>> highest, but you can modify if needed.
>>
>> $ alternatives --display sphinx-build
>> sphinx-build - status is auto.
>> link currently points to /usr/bin/sphinx-build-3.8
>> /usr/bin/sphinx-build-3.6 - priority 36
>> /usr/bin/sphinx-build-3.7 - priority 37
>> /usr/bin/sphinx-build-3.8 - priority 38
>> Current `best' version is /usr/bin/sphinx-build-3.8.
>>
>> $ /usr/bin/sphinx-build-3.8
>> usage: sphinx-build-3.8 [OPTIONS] SOURCEDIR OUTPUTDIR [FILENAMES...]
>> sphinx-build-3.8: error: the following arguments are required:
>> sourcedir, outputdir, filenames
>>
>> $ /usr/bin/sphinx-build
>> usage: sphinx-build [OPTIONS] SOURCEDIR OUTPUTDIR [FILENAMES...]
>> sphinx-build: error: the following arguments are required: sourcedir,
>> outputdir, filenames
>>
>> Regards
>> Marco
>>
>
next prev parent reply other threads:[~2020-08-10 4:58 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 [this message]
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=CAExoBLuBG+WeysC6O3ubenVSPtcW-9vBcvLR9RUTxP8P+Xj0Bw@mail.gmail.com \
--to=xavier.delaruelle@gmail.com \
--cc=cygwin@cygwin.com \
--cc=marco.atzeri@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).