GNU bug report logs - #64437
gnu: python-asn1crypto: Update to 1.5.1.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 64437 in the body.
You can then email your comments to 64437 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Michael Ford <fanquake <at> gmail.com>
To: guix-patches <at> gnu.org
Subject: gnu: python-asn1crypto: Update to 1.5.1.
Date: Mon, 3 Jul 2023 15:45:19 +0100

From ec61e381b2ec733ffcf160db66a7f60990b96ba0 Mon Sep 17 00:00:00 2001
From: fanquake <fanquake <at> gmail.com>
Date: Mon, 3 Jul 2023 15:43:00 +0100
Subject: [PATCH] gnu: python-asn1crypto: Update to 1.5.1.

---
 gnu/packages/python-crypto.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/python-crypto.scm b/gnu/packages/python-crypto.scm
index 44babe5c8c..f25ad8851d 100644
--- a/gnu/packages/python-crypto.scm
+++ b/gnu/packages/python-crypto.scm
@@ -736,7 +736,7 @@ (define-public python-pyaes
 (define-public python-asn1crypto
   (package
     (name "python-asn1crypto")
-    (version "1.4.0")
+    (version "1.5.1")
     (source
      (origin
        (method git-fetch)
@@ -746,7 +746,7 @@ (define-public python-asn1crypto
        (file-name (git-file-name name version))
        (sha256
         (base32
-         "19abibn6jw20mzi1ln4n9jjvpdka8ygm4m439hplyrdfqbvgm01r"))))
+         "1qsg06qrqnzixmrm65ibg503y2gffd675h1si4jgh92s315w1jrk"))))
     (build-system python-build-system)
     (arguments
      '(#:phases (modify-phases %standard-phases
-- 
2.41.0

Message #8 received at 64437 <at> debbugs.gnu.org (full text, mbox):

From: Michael Ford <fanquake <at> gmail.com>
To: 64437 <at> debbugs.gnu.org
Subject: [PATCH] gnu: python-asn1crypto: Update to 1.5.1.
Date: Tue, 22 Aug 2023 15:56:27 +0100

[Message part 1 (text/plain, inline)]

Hi,

Just wondering if there's anything else I need to do here? Should this have
been submitted against a different branch (i.e python-team)? Unsure as
similar updates, i.e e4702777e70ef47405c01d54ede60eff01121399, have been
merged in the interim.

Thanks,

Michael

[Message part 2 (text/html, inline)]

Message #13 received at 64437-done <at> debbugs.gnu.org (full text, mbox):

From: Hilton Chain <hako <at> ultrarare.space>
To: Michael Ford <fanquake <at> gmail.com>
Cc: 64437-done <at> debbugs.gnu.org
Subject: Re: [bug#64437] gnu: python-asn1crypto: Update to 1.5.1.
Date: Thu, 24 Aug 2023 12:50:23 +0800

Hi,

On Mon, 03 Jul 2023 22:45:19 +0800,
Michael Ford wrote:
>
> From ec61e381b2ec733ffcf160db66a7f60990b96ba0 Mon Sep 17 00:00:00 2001
> From: fanquake <fanquake <at> gmail.com>
> Date: Mon, 3 Jul 2023 15:43:00 +0100
> Subject: [PATCH] gnu: python-asn1crypto: Update to 1.5.1.
>
> ---

I have added commit message to the patch and applied it as
c49c43d44c45015dc7ef251a171a48bdba0b8b5a.  Thank you!

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.