From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars-Dominik Braun Subject: Re: [bug#39028] [PATCH 5/7] gnu: python-cryptography: Update to 2.8 Date: Tue, 21 Jan 2020 11:08:52 +0100 Message-ID: <20200121100851.GB15757@zpidnp36> References: <20200113074655.11012-1-ldb@leibniz-psychology.org> <20200113074655.11012-5-ldb@leibniz-psychology.org> <87k15mi8ax.fsf@member.fsf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33979) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itqSs-0007RN-4o for guix-devel@gnu.org; Tue, 21 Jan 2020 05:08:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1itqSr-0004Rl-6b for guix-devel@gnu.org; Tue, 21 Jan 2020 05:08:54 -0500 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]:42301) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1itqSq-0004Qm-NP for guix-devel@gnu.org; Tue, 21 Jan 2020 05:08:53 -0500 Received: by mail-wr1-x441.google.com with SMTP id q6so2424666wro.9 for ; Tue, 21 Jan 2020 02:08:51 -0800 (PST) Content-Disposition: inline In-Reply-To: <87k15mi8ax.fsf@member.fsf.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-mx.org@gnu.org Sender: "Guix-devel" To: =?utf-8?B?5a6L5paH5q2m?= Cc: guix-devel@gnu.org, 39028@debbugs.gnu.org Hi, > Hello Braun, I have pushed the previous 4 patches into master, thank you! thanks. > This is not a small change for me, as 'guix refresh -l python-cryptography' says: > Building the following 167 packages would ensure 367 dependent packages are rebuilt... True, I did not check that, my bad. Would it be acceptable to package an older version of asyncssh compatible with python-cryptography 2.7? > And I'm not sure about disable tests in python-pyopenssl (in the next > patch), maybe we should update it to 19.1.0. Nope, does not fix these three testcases for me. Lars From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:33999) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itqT1-0007ef-Rl for guix-patches@gnu.org; Tue, 21 Jan 2020 05:09:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1itqT0-0004W0-MQ for guix-patches@gnu.org; Tue, 21 Jan 2020 05:09:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:40535) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1itqT0-0004Vp-Ip for guix-patches@gnu.org; Tue, 21 Jan 2020 05:09:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1itqT0-00051x-Cq for guix-patches@gnu.org; Tue, 21 Jan 2020 05:09:02 -0500 Subject: [bug#39028] [PATCH 5/7] gnu: python-cryptography: Update to 2.8 Resent-Message-ID: Date: Tue, 21 Jan 2020 11:08:52 +0100 From: Lars-Dominik Braun Message-ID: <20200121100851.GB15757@zpidnp36> References: <20200113074655.11012-1-ldb@leibniz-psychology.org> <20200113074655.11012-5-ldb@leibniz-psychology.org> <87k15mi8ax.fsf@member.fsf.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87k15mi8ax.fsf@member.fsf.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: =?UTF-8?Q?=E5=AE=8B=E6=96=87=E6=AD=A6?= Cc: guix-devel@gnu.org, 39028@debbugs.gnu.org, zimon.toutoune@gmail.com Hi, > Hello Braun, I have pushed the previous 4 patches into master, thank you! thanks. > This is not a small change for me, as 'guix refresh -l python-cryptography' says: > Building the following 167 packages would ensure 367 dependent packages are rebuilt... True, I did not check that, my bad. Would it be acceptable to package an older version of asyncssh compatible with python-cryptography 2.7? > And I'm not sure about disable tests in python-pyopenssl (in the next > patch), maybe we should update it to 19.1.0. Nope, does not fix these three testcases for me. Lars