all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jack Hill <jackhill@jackhill.us>
Cc: 55482-done@debbugs.gnu.org
Subject: bug#55482: [PATCH] gnu: botan: Update to 2.19.1.
Date: Tue, 17 May 2022 17:08:59 -0400	[thread overview]
Message-ID: <87y1yzhno4.fsf@gmail.com> (raw)
In-Reply-To: <20220517140512.1713-1-jackhill@jackhill.us> (Jack Hill's message of "Tue, 17 May 2022 10:05:12 -0400")

Hi Jack,

Jack Hill <jackhill@jackhill.us> writes:

> * gnu/packages/crypto.scm (botan): Update to 2.19.1.
> ---
>  gnu/packages/crypto.scm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> I tested this change by building Botan's two dependent packages on
> x86_64 Linux, and everything looked good.
>
> diff --git a/gnu/packages/crypto.scm b/gnu/packages/crypto.scm
> index f938d3c115..25aa745b7e 100644
> --- a/gnu/packages/crypto.scm
> +++ b/gnu/packages/crypto.scm
> @@ -946,14 +946,14 @@ (define-public rhash
>  (define-public botan
>    (package
>      (name "botan")
> -    (version "2.18.2")
> +    (version "2.19.1")
>      (source (origin
>                (method url-fetch)
>                (uri (string-append "https://botan.randombit.net/releases/"
>                                    "Botan-" version ".tar.xz"))
>                (sha256
>                 (base32
> -                "0zih8agygp39ff0dwi3fv8y7dnnzpz3y86kcgjbhzlxry49kn6jl"))))
> +                "0q2mzzg0a40prp9gwjk7d9fn8kwj6z2x6h6mzlm0hr6sxz7h0vp2"))))
>      (build-system gnu-build-system)
>      (arguments
>       '(#:phases

Applied as 423a3a6b6a, thanks!

Maxim




  reply	other threads:[~2022-05-17 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 14:05 [bug#55482] [PATCH] gnu: botan: Update to 2.19.1 Jack Hill
2022-05-17 21:08 ` Maxim Cournoyer [this message]
2022-05-17 21:12   ` Jack Hill

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y1yzhno4.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=55482-done@debbugs.gnu.org \
    --cc=jackhill@jackhill.us \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.