From: Daniel Fort <dan@digiola.com>
To: cygwin@cygwin.com, yselkowitz@cygwin.com
Subject: Re: rst2html missing from latest docutils
Date: Thu, 29 Jun 2017 18:28:00 -0000 [thread overview]
Message-ID: <CA+fGtfBXn-G0VcU6zrHh+UG7s1EAtmav+jzGAwP20rQ++KrvUQ@mail.gmail.com> (raw)
Surprised this isn't getting more attention. All of the python 2
docutils scripts are missing from the June 19 update.
> ---------- Forwarded message ----------
> From: Oleksandr Gavenko <gavenkoa@gmail.com>
> To: cygwin@cygwin.com
> Cc:
> Bcc:
> Date: Wed, 28 Jun 2017 10:39:48 +0300
> Subject: Re: rst2html missing from latest docutils
>
> bash# zgrep /bin /etc/setup/python2-docutils.lst.gz
>
> bash# zgrep /bin /etc/setup/python3-docutils.lst.gz
> usr/bin/
> usr/bin/rst2html.py
> usr/bin/rst2html5.py
> usr/bin/rst2latex.py
> usr/bin/rst2man.py
> usr/bin/rst2odt.py
> usr/bin/rst2odt_prepstyles.py
> usr/bin/rst2pseudoxml.py
> usr/bin/rst2s5.py
> usr/bin/rst2xetex.py
> usr/bin/rst2xml.py
> usr/bin/rstpep2html.py
From: Yaakov Selkowitz <yselkowitz at cygwin dot com>
To: cygwin-announce at cygwin dot com
Date: Mon, 19 Jun 2017 01:25:57 -0500
Subject: Various Python 2 and 3 modules
The following packages have been uploaded to the Cygwin distribution:
...
* python2-docutils-0.13.1-2
...
This is a mixture of some new Python packages and some updates.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2017-06-29 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 18:28 Daniel Fort [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-27 20:21 Daniel Fort
2017-06-28 7:40 ` Oleksandr Gavenko
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=CA+fGtfBXn-G0VcU6zrHh+UG7s1EAtmav+jzGAwP20rQ++KrvUQ@mail.gmail.com \
--to=dan@digiola.com \
--cc=cygwin@cygwin.com \
--cc=yselkowitz@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).