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: Wed, 12 Aug 2020 09:16:43 +0200 [thread overview]
Message-ID: <CAExoBLv9zVGrCLQDYm=oYKqUxMRhLCPvjRiNsZGCbc07yYcb0g@mail.gmail.com> (raw)
In-Reply-To: <d2df77d7-a688-8e23-3b94-b39c25890f15@gmail.com>
Le mer. 12 août 2020 à 09:03, Marco Atzeri <marco.atzeri@gmail.com> a
écrit :
> On 11.08.2020 13:21, Marco Atzeri wrote:
> > On 11.08.2020 10:56, Xavier Delaruelle wrote:
> >> 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
> >>
> >>
> >
> > Hi Xavier,
> >
> > please bottom post on this mailing list.
> >
> > Noted, but sphinxcontrib-jsmath is not available so this requires.txt
> > is not 100% accurate anyway
> >
> > Regards
> > Marco
> >
>
> Hi Xavier,
> updated dependencies for sphinx, you should see a pull also for
>
> python3X-sphinxcontrib-jsmath
>
> no need to update the cygport, if the python packages
> are available they are automatically added to the package dependencies
>
> I am now checking all requires.txt for proper package pull
>
> Sorry for inconvenience
> Marco
>
Hi Marco,
Thanks a lot for your work.
Regards,
Xavier
prev parent reply other threads:[~2020-08-12 7:16 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
2020-08-11 11:21 ` Marco Atzeri
2020-08-12 7:03 ` Marco Atzeri
2020-08-12 7:16 ` Xavier Delaruelle [this message]
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='CAExoBLv9zVGrCLQDYm=oYKqUxMRhLCPvjRiNsZGCbc07yYcb0g@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).