public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: python 3.9 packages
Date: Fri, 24 Dec 2021 12:16:48 +0100	[thread overview]
Message-ID: <1dab002d-46ef-9fa0-b0e9-7ee49731c672@gmail.com> (raw)
In-Reply-To: <87c16632-ee39-9588-a6e6-bafa06b4af7c@dronecode.org.uk>

On 24.12.2021 11:57, Jon Turney wrote:
> On 23/12/2021 20:00, Marco Atzeri wrote:
>> On 22.12.2021 14:52, airplanemath via Cygwin wrote:
>>> On Tue, Dec 21 2021, Marco Atzeri via Cygwin-announce wrote:
>>>
>>>> Several python packages have been added to the Cygwin distribution
>>>> and at the same time the updated packages for 3.6/3./3.8
>>>> have been uploaded.
>>>>
>>>> python39-pillow                         8.4.0-1
>>>
>>> Is this replacing python3[6-9]-imaging{,-tk}?  They look similar:
>>>
>>
>>
>> emh, no. They are the same thing, my fault.
>>
>> I was fooled by an upstream dependency of another package.
>>
>> It requires Pillow, but I missed to note, as I am not the maintainer,
>> that "imaging" is using the fork "Pillow"
>>
>> https://cygwin.com/packages/x86_64/python-imaging-src/python-imaging-8.4.0-1-src 
>>
>>
>> I will remove Pillow.
> 
> I guess you've done that.  calm is now reporting:
> 
> ERROR: package 'python37-matplotlib' version '3.5.1-1' requires: 
> 'python37-pillow', but nothing satisfies that
> 
> Does that need adjusting to depend on python-imaging instead?

yes thanks.

strange that the others python3X-matplotlib do not complain

Marco


  reply	other threads:[~2021-12-24 11:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 16:06 Marco Atzeri via Cygwin-announce
2021-12-22 13:52 ` airplanemath
2021-12-23 20:00   ` Marco Atzeri
2021-12-24 10:57     ` Jon Turney
2021-12-24 11:16       ` Marco Atzeri [this message]
2021-12-24 13:53         ` Jon Turney
2021-12-23 20:34 ` Russell VT
2021-12-24  6:57   ` Marco Atzeri
2022-03-20 16:00 ` deprecate pytz? Brian Inglis
2023-03-07 21:18   ` deprecate pytz? or update pytz to 2022g/2022.7.1 Brian Inglis
2023-03-07 21:35     ` marco atzeri
2023-03-08  5:11       ` Marco Atzeri
2023-03-26 20:45         ` update pytz to 2023.2/2023b tzdata Brian Inglis
2023-03-27  0:13           ` update pytz to 2023.2/2023b tzdata? Brian Inglis
2021-12-31 10:41 [ANNOUNCEMENT] Updated: python 3.9 packages Marco Atzeri via Cygwin-announce
2022-01-09 13:33 Marco Atzeri via Cygwin-announce
     [not found] <280449814.1214701.1641799592359.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-10  7:26 ` Tatsuro MATSUOKA
2022-01-10 13:09   ` marco atzeri
2022-01-10 22:45     ` Marco Atzeri
2022-01-23 11:49 Marco Atzeri via Cygwin-announce
2022-01-24  5:15 Marco Atzeri via Cygwin-announce
2022-02-27 12:00 Marco Atzeri via Cygwin-announce

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=1dab002d-46ef-9fa0-b0e9-7ee49731c672@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /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).