From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] nghttp2, mingw64-{x86_64,i686}-nghttp2
Date: Fri, 28 May 2021 17:18:56 -0600 [thread overview]
Message-ID: <1e51a907-b7cb-3961-db13-3f4b74a8ddff@SystematicSw.ab.ca> (raw)
In-Reply-To: <59806a9c-a0f4-1868-e763-4dca35e6e3a2@gmail.com>
On 2021-05-28 12:33, Marco Atzeri via Cygwin-apps wrote:
> On 28.05.2021 19:06, Brian Inglis wrote:
>> Noticing some more libraries used by curl and wget/2 that were outdated
>> and orphaned, I decided to take a look at building updates and would now
>> like to adopt them.
>>
>> The list below shows the distributed packages, links to the Git Cygwin
>> Package repos (see playground branches), Appveyor CI builds and logs
>> for those who prefer looking at those, and links to Google drive folders
>> with all the usual files and archives for others.
>>
>> I have issues building python2/27/3/36 modules, and/or which to obsolete.
>
> you can drop all.
> Python2.7 is dead upstream and Python3.6 will be at end of 2021
>
> https://www.python.org/downloads/
I would appreciate advice on how to structure obsoleting the existing packages:
python-nghttp2
python2-nghttp2
python27-nghttp2
python3-nghttp2
python36-nghttp2
given replacement packages python37-nghttp2 and python38-nghttp2.
I can define all those as empty packages for the proposed release,
but which should obsolete what to get the appropriate replacements?
Should I define the following packages e.g.:
python2-nghttp2 dummy obsoletes python-nghttp2
python27-nghttp2 dummy obsoletes python2-nghttp2
python3-nghttp2 dummy obsoletes python27-nghttp2
python36-nghttp2 dummy obsoletes python3-nghttp2
python37-nghttp2 real obsoletes python36-nghttp2
python38-nghttp2 real stands alone for now?
> Changed maintainership to you (only for them this time)
Thank you very much - appreciate that!
Repology.org dropped the extraneous maintainership adds/removes ;^>
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-05-28 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 17:06 Brian Inglis
2021-05-28 18:33 ` Marco Atzeri
2021-05-28 23:18 ` Brian Inglis [this message]
2021-05-29 4:37 ` Brian Inglis
2021-05-29 6:12 ` Marco Atzeri
2021-05-29 10:09 ` Jon Turney
2021-05-29 10:42 ` Achim Gratz
2021-05-29 11:18 ` Achim Gratz
2021-05-29 16:55 ` Brian Inglis
2021-05-29 18:01 ` Achim Gratz
2021-05-29 18:34 ` Brian Inglis
2021-05-29 16:18 ` Brian Inglis
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=1e51a907-b7cb-3961-db13-3f4b74a8ddff@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).