From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/3] Fix letsencrypt
Date: Sat, 2 Apr 2016 20:30:33 -0400 [thread overview]
Message-ID: <20160403003033.GA4959@jasmine> (raw)
In-Reply-To: <87vb429v4h.fsf@gnu.org>
On Thu, Mar 31, 2016 at 11:48:30PM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > 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?
>
> 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/
next prev parent reply other threads:[~2016-04-03 0:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 1:46 [PATCH 0/3] Fix letsencrypt Leo Famulari
2016-03-23 1:46 ` [PATCH 1/3] gnu: python-pytest: Update to 2.7.3 Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 1:46 ` [PATCH 2/3] gnu: python-cryptography, python-cryptography-vectors: Update to 1.3.1 Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 1:46 ` [PATCH 3/3] gnu: python-pyopenssl: Update to 16.0.0 Leo Famulari
2016-03-23 7:16 ` Efraim Flashner
2016-03-23 16:05 ` Leo Famulari
2016-03-23 16:12 ` [PATCH 0/3] Fix letsencrypt Leo Famulari
2016-03-25 16:29 ` Leo Famulari
2016-03-25 23:06 ` Ludovic Courtès
2016-03-29 19:56 ` Leo Famulari
2016-03-31 21:48 ` Ludovic Courtès
2016-04-03 0:30 ` Leo Famulari [this message]
2016-04-03 6:14 ` Efraim Flashner
2016-04-04 17:52 ` Leo Famulari
2016-04-04 18:12 ` Leo Famulari
2016-03-23 20:44 ` Ricardo Wurmus
2016-03-27 22:02 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160403003033.GA4959@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).