Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libsodium: security bump version to 1.0.22
Date: Fri, 15 May 2026 15:34:24 +0200	[thread overview]
Message-ID: <20260515133424.317261-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260503060906.600090-1-bernd@kuhls.net>

In reply of:
> https://github.com/jedisct1/libsodium/releases/tag/1.0.22-RELEASE
> https://github.com/jedisct1/libsodium/releases/tag/1.0.21-RELEASE
> 
> Updated license hash due to copyright year bump:
> https://github.com/jedisct1/libsodium/commit/80c6bab4518aecd197d830c145b5d23e9b932ea3
> 
> Switched to bz2 tarball provided by upstream.
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to 2025.02.x & 2026.02.x. Thanks

> ---
>  package/libsodium/libsodium.hash | 6 +++---
>  package/libsodium/libsodium.mk   | 3 ++-
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/package/libsodium/libsodium.hash b/package/libsodium/libsodium.hash
> index ae4765a2ab..ef982ea759 100644
> --- a/package/libsodium/libsodium.hash
> +++ b/package/libsodium/libsodium.hash
> @@ -1,4 +1,4 @@
>  # Locally calculated after checking Minisign signature
> -# https://download.libsodium.org/libsodium/releases/libsodium-1.0.20.tar.gz.minisig
> -sha256  ebb65ef6ca439333c2bb41a0c1990587288da07f6c7fd07cb3a18cc18d30ce19  libsodium-1.0.20.tar.gz
> -sha256  43964d976a6db3fb986af689d05f8ca0e9971878bccae709750dac8fdc4a99cf  LICENSE
> +# https://download.libsodium.org/libsodium/releases/libsodium-1.0.22.tar.bz2.minisig
> +sha256  51b93737bf62e8549b0e94dce0fba92169e31c8ecc160883460a9bdaa6d2c298  libsodium-1.0.22.tar.bz2
> +sha256  508a76d186356c0dd807a670ef510964f8724557024796a2c426c6c0e19ab683  LICENSE
> diff --git a/package/libsodium/libsodium.mk b/package/libsodium/libsodium.mk
> index 7dd763e145..5f62a66246 100644
> --- a/package/libsodium/libsodium.mk
> +++ b/package/libsodium/libsodium.mk
> @@ -4,8 +4,9 @@
>  #
>  ################################################################################
>  
> -LIBSODIUM_VERSION = 1.0.20
> +LIBSODIUM_VERSION = 1.0.22
>  LIBSODIUM_SITE = https://download.libsodium.org/libsodium/releases
> +LIBSODIUM_SOURCE = libsodium-$(LIBSODIUM_VERSION).tar.bz2
>  LIBSODIUM_LICENSE = ISC
>  LIBSODIUM_LICENSE_FILES = LICENSE
>  LIBSODIUM_INSTALL_STAGING = YES
> -- 
> 2.47.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-05-15 13:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03  6:09 [Buildroot] [PATCH 1/1] package/libsodium: security bump version to 1.0.22 Bernd Kuhls
2026-05-03 16:01 ` Julien Olivain via buildroot
2026-05-15 13:34 ` Thomas Perale via buildroot [this message]

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=20260515133424.317261-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=thomas.perale@mind.be \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox