From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Michael Nosthoff via buildroot <buildroot@buildroot.org>
Cc: Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/spdlog: bump to version 1.17.0
Date: Wed, 7 Jan 2026 23:26:42 +0100 [thread overview]
Message-ID: <20260107232642.7af69605@windsurf> (raw)
In-Reply-To: <20260107142018.131972-1-buildroot@heine.tech>
On Wed, 7 Jan 2026 15:20:15 +0100
Michael Nosthoff via buildroot <buildroot@buildroot.org> wrote:
> Changelog: https://github.com/gabime/spdlog/releases/tag/v1.17.0
>
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
> ---
> package/spdlog/spdlog.hash | 2 +-
> package/spdlog/spdlog.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Thanks for the update, but this patch breaks legal-info for this
package:
ERROR: while checking hashes from package/spdlog/spdlog.hash
ERROR: LICENSE has wrong sha256 hash:
ERROR: expected: 4ccecab18d1ff0b61174fe3d6c430541625d3ddb865b0d5887db296f883c76e7
ERROR: got : d678c20826e1392578508e1c78649a1e3c31bda05ef4388d967dbd654461b140
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
make: *** [package/spdlog/spdlog.mk:27: spdlog-legal-info] Error 1
Could you check, and send an updated version? (Don't forget to explain
in the commit log why the license file hash has changed)
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-07 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:20 [Buildroot] [PATCH] package/spdlog: bump to version 1.17.0 Michael Nosthoff via buildroot
2026-01-07 22:26 ` Thomas Petazzoni 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=20260107232642.7af69605@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=thomas.petazzoni@bootlin.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 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.