From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Python - plan & execution
Date: Mon, 27 Apr 2020 15:34:13 +0100 [thread overview]
Message-ID: <828c5f93-d70d-1028-a8f3-8249d2c47197@dronecode.org.uk> (raw)
In-Reply-To: <03c21d5061bedff0a1be2d2fee2ecd4bd9b61362.camel@cygwin.com>
On 23/04/2020 22:54, Yaakov Selkowitz wrote:
> On Fri, 2020-04-10 at 14:52 +0200, Marco Atzeri via Cygwin-apps wrote:
>> Am 26.03.2020 um 08:19 schrieb Yaakov Selkowitz:
>>> On Thu, 2020-03-26 at 06:54 +0100, Marco Atzeri via Cygwin-apps wrote:
>>>> Am 20.03.2020 um 04:47 schrieb Yaakov Selkowitz:
>>
>> currently we have
>>
>> 119 *python27*
>
> These are fine as is, but they also don't need to be rebuilt or updated
> any more.
>
>> 114 *python36*
>> 115 *python37*
>> 10 *python38*
>
> We don't need to _obsolete or remove python3[67]-* packages, we just
> need to track how many don't have python38-* equivalents yet.
> Obviously that's still the vast majority, since 3.8 just got updated to
> a stable version.
>
> Jon Turney, if a python-foo source package was previously building e.g.
> python27-foo, python36-foo, and python37-foo, and now starts building
> only python37-foo and python38-foo, is calm going to complain?
Yes, currently it will complain about that ("install packages from
source package '...' have non-unique current versions")
calm is currently smart enough to exclude old soversions from that
check, so I guess perhaps that it needs to be taught about python27 as well.
next prev parent reply other threads:[~2020-04-27 14:57 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 3:47 Putting packages up for adoption Yaakov Selkowitz
2020-03-20 5:04 ` Marco Atzeri
2020-03-20 6:05 ` ASSI
2020-03-20 10:19 ` Corinna Vinschen
2020-03-20 10:23 ` Corinna Vinschen
2020-03-20 8:13 ` Hamish McIntyre-Bhatty
2020-03-20 8:28 ` Marco Atzeri
2020-03-20 9:29 ` Jan Nijtmans
2020-03-20 10:22 ` Corinna Vinschen
2020-03-22 22:34 ` Yaakov Selkowitz
2020-03-23 12:07 ` Jan Nijtmans
2020-03-23 15:45 ` Yaakov Selkowitz
2020-03-23 21:04 ` Jan Nijtmans
2020-03-23 23:37 ` Yaakov Selkowitz
2020-03-24 11:41 ` Jan Nijtmans
2020-03-24 13:51 ` Yaakov Selkowitz
2020-03-24 14:11 ` Jan Nijtmans
2020-03-24 14:24 ` Yaakov Selkowitz
2020-03-24 19:27 ` Jan Nijtmans
2020-04-01 9:10 ` Jan Nijtmans
2020-03-20 10:19 ` Corinna Vinschen
2020-03-20 12:11 ` Jon Turney
2020-03-24 20:19 ` Andrew Schulman
2020-04-01 20:58 ` Yaakov Selkowitz
2020-04-02 7:35 ` Corinna Vinschen
2020-07-21 0:33 ` Andrew Schulman
2020-03-20 12:09 ` Jon Turney
2020-03-21 12:47 ` Thomas Wolff
2020-03-21 14:10 ` Jon Turney
2020-03-20 12:31 ` Marco Atzeri
2020-03-20 17:32 ` Achim Gratz
2020-03-20 19:16 ` Hamish McIntyre-Bhatty
2020-03-20 19:22 ` Yaakov Selkowitz
2020-03-20 20:30 ` Marco Atzeri
2020-03-22 15:34 ` ASSI
2020-03-22 16:36 ` ASSI
2020-03-22 19:49 ` Yaakov Selkowitz
2020-03-22 20:39 ` Achim Gratz
2020-03-22 19:03 ` Achim Gratz
2020-03-23 17:14 ` ASSI
2020-03-23 23:06 ` Marco Atzeri
2020-03-20 16:17 ` Doug Henderson
2020-03-21 14:12 ` Jon Turney
2020-03-26 5:54 ` Marco Atzeri
2020-03-26 7:19 ` Yaakov Selkowitz
2020-03-27 17:52 ` Marco Atzeri
2020-03-27 20:52 ` Yaakov Selkowitz
2020-03-28 3:33 ` Marco Atzeri
2020-03-30 6:01 ` Yaakov Selkowitz
2020-03-27 17:53 ` Marco Atzeri
2020-03-27 18:32 ` Hamish McIntyre-Bhatty
2020-03-27 19:10 ` Yaakov Selkowitz
2020-03-27 20:02 ` Hamish McIntyre-Bhatty
2020-04-10 12:52 ` Python - plan & execution Marco Atzeri
2020-04-23 21:54 ` Yaakov Selkowitz
2020-04-27 14:34 ` Jon Turney [this message]
2020-05-25 4:52 ` Marco Atzeri
2020-05-25 13:43 ` Jon Turney
2020-05-25 23:45 ` Yaakov Selkowitz
2020-05-26 4:31 ` Marco Atzeri
2020-06-08 19:20 ` Jon Turney
2020-06-08 20:02 ` Marco Atzeri
2020-06-09 13:20 ` Jon Turney
2020-06-09 19:16 ` Marco Atzeri
2020-06-12 14:44 ` Jon Turney
2020-05-25 5:02 ` Marco Atzeri
2020-07-07 18:40 ` Marco Atzeri
2020-07-09 23:52 ` airplanemath
2020-07-10 5:34 ` Marco Atzeri
2020-04-04 3:17 ` Putting packages up for adoption Marco Atzeri
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=828c5f93-d70d-1028-a8f3-8249d2c47197@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).