public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com, Jari Aalto <jari.aalto@cante.net>
Subject: Re: O: pylint, python-logilab-*, python-paramiko, spambayes (python package collisions)
Date: Fri, 05 Jan 2018 06:47:00 -0000	[thread overview]
Message-ID: <d75829fa-1737-8944-cc2f-833888a0fe87@cygwin.com> (raw)
In-Reply-To: <0930f9db-a25a-22b9-e5f4-c2661ac7eedc@cygwin.com>


[-- Attachment #1.1: Type: text/plain, Size: 694 bytes --]

On 2017-12-06 21:48, Yaakov Selkowitz wrote:
> On 2017-11-19 19:10, Yaakov Selkowitz wrote:
>> While we're at it, your two remaining Python module packages
>> (python-crypto and python-feedparser) are both due for updates and split
>> wheel builds for Python 2 and 3; the former also needs some patches from
>> Fedora for a CVE and Python 3 compatibility.
>>
>> Also, as noted a month ago, pristine-tar needs to be rebuilt for Perl
>> 5.26, and sendxmpp should be rebuilt to get rid of the unwanted
>> .packlist file.  Please note that maintainers are expected to be
>> subscribed to the lists so as not to miss these issues when they arise.
> 
> Ping?

Ping 2?

-- 
Yaakov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2018-01-05  6:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16  0:54 Jari: python package collisions Yaakov Selkowitz
2017-11-19 16:53 ` O: pylint, python-logilab-*, python-paramiko, spambayes (python package collisions) Jari Aalto
2017-11-20  1:10   ` Yaakov Selkowitz
2017-12-07  3:48     ` Yaakov Selkowitz
2018-01-05  6:47       ` Yaakov Selkowitz [this message]
2018-03-02 20:26         ` Yaakov Selkowitz

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=d75829fa-1737-8944-cc2f-833888a0fe87@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=jari.aalto@cante.net \
    /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).