From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libsodium: security bump version to 1.0.22
Date: Sun, 03 May 2026 18:01:54 +0200 [thread overview]
Message-ID: <2d9137ee4cf00e3a60cab2b96db144c7@free.fr> (raw)
In-Reply-To: <20260503060906.600090-1-bernd@kuhls.net>
On 03/05/2026 08:09, Bernd Kuhls wrote:
> 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 master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-05-03 16:02 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 [this message]
2026-05-15 13:34 ` Thomas Perale via buildroot
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=2d9137ee4cf00e3a60cab2b96db144c7@free.fr \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=ju.o@free.fr \
/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