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: Thu, 31 Mar 2016 23:48:30 +0200 Message-ID: <87vb429v4h.fsf@gnu.org> References: <20160323161220.GD2063@jasmine> <20160325162923.GA5173@jasmine> <87h9fu40pt.fsf@gnu.org> <20160329195603.GA19843@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48694) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alkSC-0005AV-2s for guix-devel@gnu.org; Thu, 31 Mar 2016 17:48:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1alkS8-0007WK-TH for guix-devel@gnu.org; Thu, 31 Mar 2016 17:48:36 -0400 In-Reply-To: <20160329195603.GA19843@jasmine> (Leo Famulari's message of "Tue, 29 Mar 2016 15:56:03 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Cc: guix-devel@gnu.org Leo Famulari skribis: > On Sat, Mar 26, 2016 at 12:06:06AM +0100, Ludovic Court=C3=A8s wrote: >> Leo Famulari skribis: >>=20 >> > 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 letsencry= pt >> >> > 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. >>=20 >> Yes, I think that=E2=80=99s a reasonable approach. >>=20 >> Thank you, and sorry for the delay! > > Okay, now that we have released, what should we do about this branch? Could you rebase it on top of current master, and then ask Mark to set it up on Hydra? (I can take care of Hydra tomorrow if Mark is unavailable now.) Thanks! Ludo=E2=80=99.