From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Should we upgrade openssl?
Date: Fri, 19 Apr 2019 12:56:35 -0400 [thread overview]
Message-ID: <20190419165635.GA15108@jasmine.lan> (raw)
In-Reply-To: <87d0lkbyua.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Wed, Apr 17, 2019 at 02:28:13PM +0200, Ludovic Courtès wrote:
> Merging ‘core-updates’ is no longer an option for 1.0: I’m seriously
> still aiming for around April 30th. Let’s get our act together!
>
> Likewise, I don’t think the OpenSSL upgrade can be merged on time. But
> that’s OK: we can start working on it and have it merged as soon as
> possible, possibly with all of ‘core-updates’.
I agree, it's not feasible to implement and test this OpenSSL upgrade
for an April 30th deployment. But we do need to do the upgrade during
2019, because OpenSSL 1.0.2 will become unsupported when this year ends.
It shouldn't be too bad because all the other distros are working on it
too, if they have not already finished the upgrade. At this point many
of the users have been adjusted to work with 1.1.1.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-04-19 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 14:10 Should we upgrade openssl? Christopher Lemmer Webber
2019-04-16 20:17 ` Ludovic Courtès
2019-04-17 6:09 ` Gábor Boskovits
2019-04-17 12:28 ` Ludovic Courtès
2019-04-17 12:31 ` Gábor Boskovits
2019-04-18 17:15 ` Ludovic Courtès
2019-04-19 16:56 ` Leo Famulari [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190419165635.GA15108@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).