From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: OpenSSL package updates
Date: Sat, 06 Nov 2021 20:59:56 +0100 [thread overview]
Message-ID: <87mtmhkqbn.fsf@Rainer.invalid> (raw)
In-Reply-To: <YYa6Ro7/tQNsYuNU@calimero.vinschen.de> (Corinna Vinschen via Cygwin-apps's message of "Sat, 6 Nov 2021 18:24:22 +0100")
Corinna Vinschen via Cygwin-apps writes:
> That started with OpenSSL 0.9.5 I think, I'm not sure anymore. You
> should be able to do this in a single step, as long as you craft the
> dependencies so that an update of the openssl package pulls in the
> openssl10 package with the old lib. As soon as all dependent distro
> packages are updated, you can just drop the dependency and then the old
> package entirely.
I was hoping there was a precedent we could use for this.
The idea would be that the old openssl dependencies are all converted to
point to mingw64-*-openssl10 instead and the old packages either renamed
or removed before the (final?) update to mingw64-*-openssl-1.0.2u+za.
Then drop in mingw64-*-openssl-1.1.1l openssl, which most packages that
are still actively maintained would probably need anyway during one of
their next updates.
The packages that are affected:
mingw64-*-botan
mingw64-*-curl
mingw64-*-gnome-vfs
mingw64-*-gstreamer
mingw64-*-libevent
mingw64-*-libgda
mingw64-*-liboauth
mingw64-*-libshout
mingw64-*-libssl2
mingw64-*-libzip
mingw64-*-mariadb-connector
mingw64-*-neon
mingw64-*-nghttp
mingw64-*-opusfile
mingw64-*-postgresql
mingw64-*-qca
mingw64-*-qt4
mingw64-*-qt5-base
mingw64-*-glib2
mingw64-*-unbound
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2021-11-06 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 15:25 Achim Gratz
2021-11-06 15:58 ` Achim Gratz
2021-11-06 17:24 ` Corinna Vinschen
2021-11-06 19:59 ` Achim Gratz [this message]
2021-11-06 21:17 ` Corinna Vinschen
2021-11-07 9:44 ` Achim Gratz
2021-11-07 11:39 ` 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=87mtmhkqbn.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).