On Thu, Mar 31, 2016 at 11:48:30PM +0200, Ludovic Courtès wrote: > Leo Famulari <l...@famulari.name> skribis: > > > On Sat, Mar 26, 2016 at 12:06:06AM +0100, Ludovic Courtès wrote: > >> Leo Famulari <l...@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? > > 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/
