From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [PATCH 0/3] Fix letsencrypt
Date: Sat, 26 Mar 2016 00:06:06 +0100
Message-ID: <87h9fu40pt.fsf@gnu.org>
References: <cover.1458697233.git.leo@famulari.name>
	<20160323161220.GD2063@jasmine> <20160325162923.GA5173@jasmine>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34192)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1ajao1-0007nP-NK
	for guix-devel@gnu.org; Fri, 25 Mar 2016 19:06:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1ajanw-0002cm-OX
	for guix-devel@gnu.org; Fri, 25 Mar 2016 19:06:13 -0400
In-Reply-To: <20160325162923.GA5173@jasmine> (Leo Famulari's message of "Fri,
	25 Mar 2016 12:29:23 -0400")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org

Leo Famulari <leo@famulari.name> skribis:

> On Wed, Mar 23, 2016 at 12:12:20PM -0400, Leo Famulari wrote:
>> On Tue, Mar 22, 2016 at 09:46:09PM -0400, Leo Famulari wrote:
>> > Earlier today I found that I could not build letsencrypt.
>> >=20
>> > The recent update to python-hypothesis broke python-pyopenssl, which
>> > blocked the build of letsencrypt.
>> >=20
>> > This patch series seems to be the minimum required to get letsencrypt
>> > building again. I built letsencrypt on these patches and used it to
>> > issue certificates for a new server.
>> >=20
>> > The update to python-pytest and python2-pytest will require ~200
>> > rebuilds [0].
>>=20
>> Any advice on where to apply these patches?
>
> I pushed the branch 'fix-letsencrypt' to Savannah. My understanding is
> that we will merge it after the next release.

Yes, I think that=E2=80=99s a reasonable approach.

Thank you, and sorry for the delay!

Ludo=E2=80=99.