From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Famulari <leo@famulari.name>
Subject: Re: [PATCH] python-cryptography update
Date: Tue, 8 Nov 2016 11:01:09 -0500
Message-ID: <20161108160109.GA19400@jasmine>
References: <87zila6lok.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59032)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1c48pq-0001Ob-Eu
	for guix-devel@gnu.org; Tue, 08 Nov 2016 11:01:19 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1c48pm-0001BD-Ga
	for guix-devel@gnu.org; Tue, 08 Nov 2016 11:01:18 -0500
Received: from out4-smtp.messagingengine.com ([66.111.4.28]:35292)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <leo@famulari.name>) id 1c48pm-0001A3-C3
	for guix-devel@gnu.org; Tue, 08 Nov 2016 11:01:14 -0500
Content-Disposition: inline
In-Reply-To: <87zila6lok.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org

On Tue, Nov 08, 2016 at 03:22:35PM +0000, Marius Bakke wrote:
> 
> The latest version of python-cryptography contains a security fix:
> 
> https://cryptography.io/en/latest/changelog/#id1
> 
> However, updating requires pytest > 2.9 which we only have in
> core-updates. Is it okay to cherry-pick 0bc6ef2 "gnu: Add
> python-pytest-2.9.2" to master?

Yes, please do it. Certbot builds with these changes, so I think it's
fine.