From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/libressl: bump to version 3.8.4
Date: Mon, 1 Apr 2024 16:17:32 +0200 [thread overview]
Message-ID: <ZgrB_CpdJbJOmv3T@landeda> (raw)
In-Reply-To: <20240328174052.8677-1-francois.perrad@gadz.org>
François, All,
On 2024-03-28 18:40 +0100, Francois Perrad spake thusly:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
Again, yiour From and SoB do not match: fperrad@gmail.com vs.
francois.perrad@gadz.org.
This applies to other patches, too:
package/graphene: new package
package/libgtk4: new package
package/lmdb: new package
package/lua-lightningmdb: new package
package/lua-lgdbm: new package
package/lua-lsdbus: new package
package/libtommath: bump to version 1.3.0
Can you fix and respin, please?
Regards,
Yann E. MORIN.
> ---
> package/libressl/libressl.hash | 2 +-
> package/libressl/libressl.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/libressl/libressl.hash b/package/libressl/libressl.hash
> index 40b49dbb8..5d3b54ea9 100644
> --- a/package/libressl/libressl.hash
> +++ b/package/libressl/libressl.hash
> @@ -1,4 +1,4 @@
> # From https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/SHA256
> -sha256 6d4b8d5bbb25a1f8336639e56ec5088052d43a95256697a85c4ce91323c25954 libressl-3.8.2.tar.gz
> +sha256 c0cef9cfe174ac366ce482f542fddb07721e7fa0caface34b49a8720fa37fe7d libressl-3.8.4.tar.gz
> # Locally computed
> sha256 5c63613f008f16a9c0025c096bbd736cecf720494d121b5c5203e0ec6e5955b1 COPYING
> diff --git a/package/libressl/libressl.mk b/package/libressl/libressl.mk
> index b72f3b38c..1d90aa853 100644
> --- a/package/libressl/libressl.mk
> +++ b/package/libressl/libressl.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -LIBRESSL_VERSION = 3.8.2
> +LIBRESSL_VERSION = 3.8.4
> LIBRESSL_SITE = https://ftp.openbsd.org/pub/OpenBSD/LibreSSL
> LIBRESSL_LICENSE = ISC (new additions), OpenSSL or SSLeay (original OpenSSL code)
> LIBRESSL_LICENSE_FILES = COPYING
> --
> 2.40.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-01 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 17:40 [Buildroot] [PATCH] package/libressl: bump to version 3.8.4 Francois Perrad
2024-04-01 14:17 ` Yann E. MORIN [this message]
2024-04-01 15:11 ` François Perrad
2024-04-01 15:27 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2024-04-03 8:42 Francois Perrad
2024-04-03 20:32 ` Yann E. MORIN
2024-05-01 20:17 ` Peter Korsgaard
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=ZgrB_CpdJbJOmv3T@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
--cc=fperrad@gmail.com \
/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