emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#60304: closed ([PATCH core-updates] gnu: libksba: Update to 1.6.3.)


From: GNU bug Tracking System
Subject: bug#60304: closed ([PATCH core-updates] gnu: libksba: Update to 1.6.3.)
Date: Fri, 30 Dec 2022 16:53:01 +0000

Your message dated Fri, 30 Dec 2022 17:52:16 +0100
with message-id <a2d2e6bbe36bf462e1339b6d4ff6479a@tobias.gr>
and subject line Re: [bug#60304] [PATCH core-updates] gnu: libksba: Update to 
1.6.3.
has caused the debbugs.gnu.org bug report #60304,
regarding [PATCH core-updates] gnu: libksba: Update to 1.6.3.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
60304: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60304
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH core-updates] gnu: libksba: Update to 1.6.3. Date: Sun, 25 Dec 2022 00:28:00 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Hi.  

This patch updates libksba to 1.6.3 on the core-updates branch, which
goes together with the security graft to 'master' that I posted here:
https://lists.gnu.org/archive/html/guix-patches/2022-12/msg01053.html

I have built it and tried to test it, but I'm not certain what a good
way to test that a newly built package works as expected, so I'm looking
for feedback.

/Simon
From c4cccf53eb931493192af1f8e5bd52bbf1779664 Mon Sep 17 00:00:00 2001
From: Simon Josefsson <simon@josefsson.org>
Date: Sun, 25 Dec 2022 00:19:28 +0100
Subject: [PATCH core-updates] gnu: libksba: Update to 1.6.3.

* gnu/packages/gnupg.scm (libksba): Update to 1.6.3.
---
 gnu/packages/gnupg.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
index e04c4671b4..6c103a4b36 100644
--- a/gnu/packages/gnupg.scm
+++ b/gnu/packages/gnupg.scm
@@ -233,7 +233,7 @@ (define-public libassuan
 (define-public libksba
   (package
     (name "libksba")
-    (version "1.6.1")
+    (version "1.6.3")
     (source
      (origin
       (method url-fetch)
@@ -242,7 +242,7 @@ (define-public libksba
             version ".tar.bz2"))
       (sha256
        (base32
-        "017aqq619yl1br46ghiw39n1yrh3cvdkhy926c4gl4faqdj0hxa0"))))
+        "0p6y82j9y6n0l7scjgqhz3as9w13jiqjfx9n2jzynw89nf6wcwiz"))))
     (build-system gnu-build-system)
     (propagated-inputs
      (list libgpg-error))
-- 
2.38.1

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: [bug#60304] [PATCH core-updates] gnu: libksba: Update to 1.6.3. Date: Fri, 30 Dec 2022 17:52:16 +0100
Hi Simon,

On 2022-12-25 0:28, Simon Josefsson via Guix-patches via wrote:
This patch updates libksba to 1.6.3 on the core-updates branch

Thanks! Pushed as b8d684af76a41f5856b73640eb6f21940f214497 on core-updates. Someone's working on updating gnupg there.

I have built it and tried to test it, but I'm not certain what a good
way to test that a newly built package works as expected, so I'm looking
for feedback.

I don't have a universal answer handy, but in this case I just built & installed the corresponding gnupg package. Then I restarted the agent and did stuff: sign the above commit; ssh into a box; … It worked.

Also, users are already running gnupg built against libksba@1.6.2 with libksba@1.6.3 thanks to your graft, and I haven't heard any complaints yet.

Kind regards,

T G-R

Sent from a Web browser.  Excuse or enjoy my brevity.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]