From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Famulari <leo@famulari.name>
Subject: Re: [PATCH 0/3] Fix letsencrypt
Date: Tue, 29 Mar 2016 15:56:03 -0400
Message-ID: <20160329195603.GA19843@jasmine>
References: <cover.1458697233.git.leo@famulari.name>
	<20160323161220.GD2063@jasmine> <20160325162923.GA5173@jasmine>
	<87h9fu40pt.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54950)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1akzkF-0002s4-7C
	for guix-devel@gnu.org; Tue, 29 Mar 2016 15:56:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1akzkB-0001TA-17
	for guix-devel@gnu.org; Tue, 29 Mar 2016 15:56:07 -0400
Received: from out4-smtp.messagingengine.com ([66.111.4.28]:47495)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1akzkA-0001Sw-TT
	for guix-devel@gnu.org; Tue, 29 Mar 2016 15:56:02 -0400
Content-Disposition: inline
In-Reply-To: <87h9fu40pt.fsf@gnu.org>
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: Ludovic =?iso-8859-1?Q?Court=E8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org

On Sat, Mar 26, 2016 at 12:06:06AM +0100, Ludovic Courtès wrote:
> 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.
> >> > 
> >> > The recent update to python-hypothesis broke python-pyopenssl, which
> >> > blocked the build of letsencrypt.
> >> > 
> >> > 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.
> >> > 
> >> > The update to python-pytest and python2-pytest will require ~200
> >> > rebuilds [0].
> >> 
> >> 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’s a reasonable approach.
> 
> Thank you, and sorry for the delay!

Okay, now that we have released, what should we do about this branch?