From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: [ITA] nghttp2, mingw64-{x86_64,i686}-nghttp2
Date: Fri, 28 May 2021 11:06:13 -0600 [thread overview]
Message-ID: <ad78a64a-2867-3599-f10e-bc7a184e9a92@SystematicSw.ab.ca> (raw)
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.
I would like to get all this sorted and updated before updating the latest
curl release now available.
Feedback and questions welcome.
Binaries Last Proposed Source
nghttp2 1.37.0-1 1.43.0-1 source
nghttp2-debuginfo 1.37.0-1 1.43.0-1
libnghttp2_14 1.37.0-1 1.43.0-1
libnghttp2-devel 1.37.0-1 1.43.0-1
python-nghttp2 1.37.0-1 obsolete?
python2-nghttp2 1.37.0-1 obsolete?
python27-nghttp2 1.37.0-1 obsolete?
python3-nghttp2 1.37.0-1 obsolete?
python36-nghttp2 1.37.0-1 obsolete?
python37-nghttp2 1.37.0-1 1.43.0-1
python38-nghttp2 new 1.43.0-1
mingw64-i686-nghttp2 1.31.0-1 1.43.0-1 source
mingw64-x86_64-nghttp2 1.31.0-1 1.43.0-1 source
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/nghttp2.git;a=summary
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/mingw64-x86_64-nghttp2.git;a=summary
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/mingw64-i686-nghttp2.git;a=summary
https://ci.appveyor.com/project/cygwin/scallywag/builds/39370115
https://ci.appveyor.com/api/buildjobs/48gfcwh89ip3ts2g/log
https://ci.appveyor.com/api/buildjobs/5pggx6no64rhjdbv/log
https://drive.google.com/drive/folders/1Ee4KNQ6EaTnh8MkqbLNxnEpBaw3JOaFk
--
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 reply other threads:[~2021-05-28 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 17:06 Brian Inglis [this message]
2021-05-28 18:33 ` Marco Atzeri
2021-05-28 23:18 ` Brian Inglis
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=ad78a64a-2867-3599-f10e-bc7a184e9a92@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).