public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Tue, 11 Aug 2020 10:56:32 +0200	[thread overview]
Message-ID: <CAExoBLtNM3rLC1Vr+31POrpwGJUXLFDt=JjwbmrcBODoWUoD+A@mail.gmail.com> (raw)
In-Reply-To: <CAExoBLvPpeJgrCS_bAAJ6C=Mj-fb37xHgp4N6LYJSb7ge-biaA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3162 bytes --]

Hello,

I confirm that my documentation build is ok (log at [1]) with the following
extension package installed on top of python37-sphinx

python37-sphinxcontrib-serializinghtml
python37-sphinxcontrib-applehelp
python37-sphinxcontrib-devhelp
python37-sphinxcontrib-htmlhelp
python37-sphinxcontrib-qthelp

Looking at Sphinx project sources, it seems that even if these *builders*
have been moved aside in separate projects starting version 2, they are
still mandatory for sphinx core to operate. Looking at the
Sphinx.egg-info/requires.txt file in source tarball, we can find at the
beginning:

sphinxcontrib-applehelp
sphinxcontrib-devhelp
sphinxcontrib-jsmath
sphinxcontrib-htmlhelp
sphinxcontrib-serializinghtml
sphinxcontrib-qthelp

So to honor those requirements, I think the sphinx cygport file should be
updated like in the attached patch.

Regards,
Xavier

[1]
https://ci.appveyor.com/project/xdelaruelle/modules/builds/34591628/job/6u76k02d4uriq91q

Le lun. 10 août 2020 à 10:39, Xavier Delaruelle <xavier.delaruelle@gmail.com>
a écrit :

> Can you update the requirements of python*-sphinx packages to make these
> new packages automatically installed when python*-sphinx is installed ? (as
> they seem required to build any sphinx documentation)
>
> Regards,
> Xavier
>
> Le lun. 10 août 2020 à 10:11, Marco Atzeri <marco.atzeri@gmail.com> a
> écrit :
>
>> 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
>>
>>

[-- Attachment #2: sphinxcontrib_requirements.patch --]
[-- Type: text/x-patch, Size: 1388 bytes --]

--- python-sphinx.cygport.orig	2020-08-11 10:50:10.425907774 +0200
+++ python-sphinx.cygport	2020-08-11 10:52:53.439267803 +0200
@@ -15,9 +15,9 @@
 
 ARCH=noarch
 
-python36_sphinx_REQUIRES="python36-alabaster python36-sphinx_rtd_theme python36-sphinxcontrib-websupport"
-python37_sphinx_REQUIRES="python37-alabaster python37-sphinx_rtd_theme python37-sphinxcontrib-websupport"
-python38_sphinx_REQUIRES="python37-alabaster python37-sphinx_rtd_theme python38-sphinxcontrib-websupport"
+python36_sphinx_REQUIRES="python36-alabaster python36-sphinx_rtd_theme python36-sphinxcontrib-websupport python36-sphinxcontrib-serializinghtml python36-sphinxcontrib-applehelp python36-sphinxcontrib-devhelp python36-sphinxcontrib-htmlhelp python36-sphinxcontrib-qthelp"
+python37_sphinx_REQUIRES="python37-alabaster python37-sphinx_rtd_theme python37-sphinxcontrib-websupport python37-sphinxcontrib-serializinghtml python37-sphinxcontrib-applehelp python37-sphinxcontrib-devhelp python37-sphinxcontrib-htmlhelp python37-sphinxcontrib-qthelp"
+python38_sphinx_REQUIRES="python38-alabaster python38-sphinx_rtd_theme python38-sphinxcontrib-websupport python38-sphinxcontrib-serializinghtml python38-sphinxcontrib-applehelp python38-sphinxcontrib-devhelp python38-sphinxcontrib-htmlhelp python38-sphinxcontrib-qthelp"
 
 python36_sphinx_CONTENTS+=" usr/bin/sphinx-*3.6
 etc/postinstall/python36-sphinx.sh

  reply	other threads:[~2020-08-11  8:56 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
2020-08-10  8:39                 ` Xavier Delaruelle
2020-08-11  8:56                   ` Xavier Delaruelle [this message]
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='CAExoBLtNM3rLC1Vr+31POrpwGJUXLFDt=JjwbmrcBODoWUoD+A@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).