From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 0/3] Fix letsencrypt Date: Sat, 2 Apr 2016 20:30:33 -0400 Message-ID: <20160403003033.GA4959@jasmine> References: <20160323161220.GD2063@jasmine> <20160325162923.GA5173@jasmine> <87h9fu40pt.fsf@gnu.org> <20160329195603.GA19843@jasmine> <87vb429v4h.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57948) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1amVw9-0007dc-34 for guix-devel@gnu.org; Sat, 02 Apr 2016 20:30:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1amVw5-0005Zt-RC for guix-devel@gnu.org; Sat, 02 Apr 2016 20:30:41 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:37875) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1amVw5-0005Zf-Hk for guix-devel@gnu.org; Sat, 02 Apr 2016 20:30:37 -0400 Content-Disposition: inline In-Reply-To: <87vb429v4h.fsf@gnu.org> 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: Ludovic =?iso-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org On Thu, Mar 31, 2016 at 11:48:30PM +0200, Ludovic Courtès wrote: > Leo Famulari skribis: > > > On Sat, Mar 26, 2016 at 12:06:06AM +0100, Ludovic Courtès wrote: > >> Leo Famulari 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? > > 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.) I think the job is complete, although I don't understand Hydra's interface very well: http://hydra.gnu.org/jobset/gnu/fix-letsencrypt/