From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 4/4] gnu: python-enum34: Remove python-setuptools from inputs.
Date: Sun, 21 Feb 2016 08:38:59 +0200 [thread overview]
Message-ID: <20160221083859.7e33746d@debian-netbook> (raw)
In-Reply-To: <20160221054935.GA26827@jasmine>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
On Sun, 21 Feb 2016 00:49:35 -0500
Leo Famulari <leo@famulari.name> wrote:
> On Thu, Feb 18, 2016 at 10:03:32AM +0200, Efraim Flashner wrote:
> [...]
> [...]
> [...]
>
>
> I built letsencrypt, which depends on python2-enum34 via
> python2-cryptography, on this branch and successfully renewed my certs
> with it.
>
> If there are no other concerns about these patches, I'd like to apply
> them soon.
>
> [...]
>
>
LGTM!
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-02-21 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 1:44 [PATCH 0/4] Update use of python-enum34 Leo Famulari
2016-02-15 1:44 ` [PATCH 1/4] gnu: python-enum34: Update to 1.1.0 Leo Famulari
2016-02-15 1:44 ` [PATCH 2/4] gnu: Add python2-enum34 Leo Famulari
2016-02-18 8:03 ` Efraim Flashner
2016-02-18 18:03 ` Leo Famulari
2016-02-15 1:44 ` [PATCH 3/4] gnu: Don't use python-enum34 when building with python-3.4 Leo Famulari
2016-02-15 1:44 ` [PATCH 4/4] gnu: python-enum34: Remove python-setuptools from inputs Leo Famulari
2016-02-18 8:03 ` Efraim Flashner
2016-02-18 17:56 ` Leo Famulari
2016-02-18 18:13 ` Leo Famulari
2016-02-21 5:49 ` Leo Famulari
2016-02-21 6:38 ` Efraim Flashner [this message]
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=20160221083859.7e33746d@debian-netbook \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).