DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 9F11F3857C4A
MIME-Version: 1.0
References: <CAExoBLuHG2=Y5wMW0dJQD4zV1Jms29Qz_3kEQh8mbuD3s4NKEw@mail.gmail.com>
 <dda513be-8097-e0d7-eed1-0f08a9b6d6f5@gmail.com>
 <DB7PR02MB3996B71344049C4A30D84BE3E7460@DB7PR02MB3996.eurprd02.prod.outlook.com>
 <CAExoBLsyh7OPUHBqCB9U9Oq6+xkLxQ8mA4Z5JMiwW8yczBjUTw@mail.gmail.com>
 <0b776916-a68d-56c4-0b2f-306413f21587@gmail.com>
 <CAExoBLv_TkpaErqjE7OG1072Et98n7Zk9YLK465x3byCccB=3Q@mail.gmail.com>
In-Reply-To: <CAExoBLv_TkpaErqjE7OG1072Et98n7Zk9YLK465x3byCccB=3Q@mail.gmail.com>
Date: Mon, 10 Aug 2020 06:58:34 +0200
Message-ID: <CAExoBLuBG+WeysC6O3ubenVSPtcW-9vBcvLR9RUTxP8P+Xj0Bw@mail.gmail.com>
Subject: Re: Missing 'sphinx-build' command from python37-sphinx package
To: Marco Atzeri <marco.atzeri@gmail.com>
From: Xavier Delaruelle via Cygwin <cygwin@cygwin.com>
Reply-To: Xavier Delaruelle <xavier.delaruelle@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces@cygwin.com>
Content-Transfer-Encoding: 8bit

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
>>
>
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple