public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages)
Date: Thu, 28 Mar 2024 13:08:00 -0600	[thread overview]
Message-ID: <b0eb74ab-04fd-49bf-b30f-e64ca784df14@SystematicSw.ab.ca> (raw)
In-Reply-To: <65a79f01-93df-42d3-8e0f-e6f906f4d346@dronecode.org.uk>

On 2024-03-28 11:49, Jon Turney via Cygwin-apps wrote:
> On 27/03/2024 21:18, Brian Inglis via Cygwin-apps wrote:
>> On 2024-03-27 14:07, Jon Turney via Cygwin-apps wrote:
>>> On 24/03/2024 18:51, Brian Inglis via Cygwin-apps wrote:
>>>> On 2024-03-24 11:46, Jon Turney via Cygwin-apps wrote:
>>>>> On 24/03/2024 17:31, Marco Atzeri via Cygwin-apps wrote:
>>>>>> On 24/03/2024 15:07, Jon Turney wrote:
>>>>>>> On 24/09/2023 13:32, Jon Turney via Cygwin-apps wrote:
> [...]
>>>
>>> Are they supposed to migrate to some alternate bindings maybe available from 
>>> a separate repo? Or are they just out of luck?
>>
>> SOL! Dropped them in 1.52, probably why 1.31.0..1.51.0 are hanging around.
> 
> Nice :S
> 
>>>> Feel free to purge as appropriate, or tell me what to add to cygport, hints, 
>>>> etc!
>>>
>>> So, the long list of source versions will hopefully be reduced in the 
>>> fullness of time...
>>
>> Could I just add to nghttp2.cygport that nghttp2 obsoletes 
>> python{2{,7},3{,6,7,8,9}}-nghttp2?
>> Does this have to remain in the cygport forever to avoid keeping nghttp2 
>> vx.x.x around?
> 
> You could, but that's probably not the correct thing to do unless you really, 
> really want to forcibly uninstall those packages for anyone who has installed 
> them, which seems like unnecessary breakage.
> 
> I don't think you have to do anything.  There's nothing "wrong" here.
> 
> If it really offends your sense of aesthetics, I suggest you just expire some 
> subset of the old versions using the vault command [1].
> 
> [1] https://cygwin.com/package-upload.html#deleting

Great idea!

Current setup packages are:

python3-nghttp2  1.43.0-1 x86_64
python36-nghttp2 1.46.0-1 x86_64
python37-nghttp2 1.46.0-1 x86_64
python38-nghttp2 1.51.0-1 x86_64
python39-nghttp2 1.51.0-1 x86_64

and 37 obsoletes 36 obsoletes 3, so from src:

             Version      Package Size       Date            Files      Status
        1.31.0-1 (source) 1512 KiB     2018-03-16 01:07 [list of files] stable
        1.37.0-1 (source) 1593 KiB     2019-03-27 03:17 [list of files] stable
        1.43.0-1 (source) 3885 KiB     2021-05-30 06:33 [list of files] stable
        1.44.0-1 (source) 3884 KiB     2021-07-19 11:32 [list of files] stable
        1.45.1-1 (source) 3929 KiB     2021-09-26 12:08 [list of files] stable
        1.46.0-1 (source) 3936 KiB     2021-10-24 03:17 [list of files] stable
        1.49.0-1 (source) 4021 KiB     2022-08-28 01:08 [list of files] stable
        1.50.0-1 (source) 4019 KiB     2022-09-25 19:43 [list of files] stable
        1.51.0-1 (source) 4025 KiB     2022-11-13 20:42 [list of files] stable
        1.58.0-1 (source) 1515 KiB     2023-10-29 17:13 [list of files] stable
        1.59.0-1 (source) 1516 KiB     2024-01-21 19:31 [list of files] stable
        1.60.0-1 (source) 1554 KiB     2024-03-03 17:16 [list of files] stable

I should be able to vault 1.31-1.45 and 1.49-1.50, or should I also add 1.46?

Could I also selectively upload -*.tar.xz for old python package versions?

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

  reply	other threads:[~2024-03-28 19:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 21:18 Brian Inglis
2024-03-28 17:49 ` Jon Turney
2024-03-28 19:08   ` Brian Inglis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-24 12:32 Bonfire of the Packages Jon Turney
2024-03-24 14:07 ` Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages) Jon Turney
2024-03-24 17:31   ` Marco Atzeri
2024-03-24 17:46     ` Jon Turney
2024-03-24 18:51       ` Brian Inglis
2024-03-27 20:07         ` Jon Turney
2024-03-28 17:50       ` Jon Turney
2024-04-18  6:01         ` Ake Rehnman
2024-04-19 12:16           ` Jon Turney
2024-03-28 17:50       ` Jon Turney
2024-03-29 18:32         ` David Rothenberger
2024-03-30 15:25           ` Jon Turney
2024-04-01 17:16             ` David Rothenberger
2024-04-02 14:38               ` Jon Turney
2024-04-02 14:58                 ` Takashi Yano
2024-04-05 12:46                   ` Jon Turney
2024-04-05 23:17                     ` Takashi Yano
2024-04-01 15:22       ` Jon Turney

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=b0eb74ab-04fd-49bf-b30f-e64ca784df14@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).