From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sergey Bobrenok <bobrofon@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/sdbus-cpp: bump to version 1.3.0
Date: Tue, 29 Aug 2023 23:31:33 +0200 [thread overview]
Message-ID: <20230829233133.29a69227@windsurf> (raw)
In-Reply-To: <20230829191709.405687-1-bobrofon@gmail.com>
Hello Sergey,
On Tue, 29 Aug 2023 22:17:09 +0300
Sergey Bobrenok <bobrofon@gmail.com> wrote:
> Changelog:
> https://github.com/Kistler-Group/sdbus-cpp/releases/tag/v1.3.0
>
> Signed-off-by: Sergey Bobrenok <bobrofon@gmail.com>
> ---
> package/sdbus-cpp/sdbus-cpp.hash | 2 +-
> package/sdbus-cpp/sdbus-cpp.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Thanks, but this breaks legal-info:
>>> sdbus-cpp 1.3.0 Collecting legal info
COPYING: OK (sha256: 20c17d8b8c48a600800dfd14f95d5cb9ff47066a9641ddeab48dc54aec96e331)
ERROR: COPYING-LGPL-Exception has wrong sha256 hash:
ERROR: expected: be43debbf06a38325616054a39e44ed5afde4ed21b99de197488a4a306d47e39
ERROR: got : a1c9e75e25d8f2ce18017c88978edab2f0dbc7814ad0697d4ff2e5e59959f657
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
make: *** [package/sdbus-cpp/sdbus-cpp.mk:17: sdbus-cpp-legal-info] Error 1
When you update the hash for the license files, you need to explain in
the commit log why they are changed (by doing a diff of the license
file before/after, and summarize those changes).
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
next prev parent reply other threads:[~2023-08-29 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 19:17 [Buildroot] [PATCH 1/1] package/sdbus-cpp: bump to version 1.3.0 Sergey Bobrenok
2023-08-29 21:31 ` Thomas Petazzoni via buildroot [this message]
2023-08-29 22:07 ` [Buildroot] [PATCH v2] " Sergey Bobrenok
2023-08-30 21:58 ` Thomas Petazzoni 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=20230829233133.29a69227@windsurf \
--to=buildroot@buildroot.org \
--cc=bobrofon@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.