From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Should we upgrade openssl?
Date: Wed, 17 Apr 2019 14:31:51 +0200 [thread overview]
Message-ID: <CAE4v=pgCdh4f3561=6mymRcUqgzB=bcDTmFEO5pBjBWUmxc_-A@mail.gmail.com> (raw)
In-Reply-To: <87d0lkbyua.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
Hello,
Ludovic Courtès <ludo@gnu.org> ezt írta (időpont: 2019. ápr. 17., Sze
14:28):
> Hi Gábor,
>
> Gábor Boskovits <boskovits@gmail.com> skribis:
>
> > I would go for the upgrade. As this is a change affecting lots of
> packages,
> > and this upgrade would allow us to reduce the chances to stuck with a
> > vulnerable version. I also suppose, that there areg- some changes on
> > core-updates we would like to merge anyways before 1.0, so if the upgrade
> > goes smoothly, then this is not a big loss of time. Wdyt?
>
> 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!
>
Ok, that's clear.
>
> 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’.
>
Do we have a list of actionable items we can work on to help?
>
> Thoughts?
>
> Thanks,
> Ludo’.
>
Best regards,
g_bor
>
[-- Attachment #2: Type: text/html, Size: 2040 bytes --]
next prev parent reply other threads:[~2019-04-17 12:32 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 [this message]
2019-04-18 17:15 ` Ludovic Courtès
2019-04-19 16:56 ` Leo Famulari
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='CAE4v=pgCdh4f3561=6mymRcUqgzB=bcDTmFEO5pBjBWUmxc_-A@mail.gmail.com' \
--to=boskovits@gmail.com \
--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).