[debbugs-tracker] bug#29476: closed ([PATCH] gnu: libressl: Update to 2.6.3.)

[GNU bug Tracking System]

Your message dated Tue, 28 Nov 2017 13:51:24 -0500
with message-id <address@hidden>
and subject line Re: [bug#29476] [PATCH] gnu: libressl: Update to 2.6.3.
has caused the debbugs.gnu.org bug report #29476,
regarding [PATCH] gnu: libressl: Update to 2.6.3.
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
29476: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29476
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [PATCH] gnu: libressl: Update to 2.6.3. Date: Mon, 27 Nov 2017 20:04:21 +0100

Here's an update for LibreSSL.

0001-gnu-libressl-Update-to-2.6.3.patch
Description: Text Data

--- End Message ---

--- Begin Message --- Subject: Re: [bug#29476] [PATCH] gnu: libressl: Update to 2.6.3. Date: Tue, 28 Nov 2017 13:51:24 -0500 User-agent: Mutt/1.9.1 (2017-09-22)

On Tue, Nov 28, 2017 at 11:28:43AM +0100, Ludovic Courtès wrote:
> Leo Famulari <address@hidden> skribis:
> 
> > The issue I had is that Python 3.5.3 is not compatible with LibreSSL
> > 2.6, but only 2.5; I use an OpenSSH with a LibreSSL-only dependency
> > graph.
> >
> > OpenSSH itself builds fine with LibreSSL 2.6, although it does not
> > support OpenSSL 1.1. It's likely that once OpenSSL 1.0.2 is retired, the
> > portable OpenSSH will require LibreSSL, unless someone contributes
> > support for the new OpenSSL API to OpenSSH.
> >
> > Well, we don't claim to support replacing OpenSSL with LibreSSL, and
> > Python is not developed against LibreSSL, so I guess there is no good
> > reason to delay this update.
> >
> > Thoughts? I'll push if there are no objections.
> 
> Sounds good to me!

Great! Pushed as fbf5ca3c5e23a4f48e6d91d7229edca283fa86b9

signature.asc
Description: PGP signature

--- End Message ---