From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: [ITA] openssl, openssl10, mingw64-{i686,x86_64}-openssl
Date: Sun, 28 Nov 2021 10:07:55 +0100 [thread overview]
Message-ID: <87a6ho642c.fsf@Rainer.invalid> (raw)
As I wrote about a month ago:
https://sourceware.org/pipermail/cygwin-apps/2021-October/041632.html
https://sourceware.org/pipermail/cygwin-apps/2021-November/041651.html
I have updated the recently released Cygwin packages with all upstream
patches from Fedora plus the patches for all CVE affecting version 1.0.2
since the last official version and changed the cygport files so they
build on AppVeyor. The packages have been pushed to the respective
playground branches:
https://cygwin.com/git-cygwin-packages?p=git/cygwin-packages/openssl10.git;a=shortlog;h=refs/heads/playground
https://cygwin.com/git-cygwin-packages?p=git/cygwin-packages/openssl.git;a=shortlog;h=refs/heads/playground
For the MinGW64 packages the current plan (based on the previous
discussion) is to update them with the 1.0.2 version and provide the
1.1.1 version (without renaming the packages or introducing any new
package names) as a test version only. This means that the existing
packages depending on mingw64-{i686,x86_64}-openssl will still work
correctly, but can be rebuilt using the 1.1.1 version by chosing the
test version (whatever the likelyhood of that actually happening is).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next reply other threads:[~2021-11-28 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 9:07 Achim Gratz [this message]
2021-11-28 9:22 ` Marco Atzeri
2021-11-28 9:43 ` ASSI
2021-11-28 10:52 ` Marco Atzeri
2021-11-28 12:28 ` Achim Gratz
2021-11-28 10:09 ` gs-cygwin.com
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=87a6ho642c.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).