From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/supervisor: bump to version 3.4.0
Date: Sat, 7 Sep 2019 23:25:13 +0200 [thread overview]
Message-ID: <20190907232513.40485c7a@windsurf> (raw)
In-Reply-To: <20190907201408.9367-1-sam@gpsm.co.uk>
On Sat, 7 Sep 2019 21:14:08 +0100
sam at gpsm.co.uk wrote:
> From: Sam Lancia <sam@gpsm.co.uk>
>
> Signed-off-by: Sam Lancia <sam@gpsm.co.uk>
> ---
> package/supervisor/supervisor.hash | 2 +-
> package/supervisor/supervisor.mk | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Thanks, but this break "make legal-info", because the hash of the
license file has changed:
>>> supervisor 3.4.0 Patching
>>> supervisor 3.4.0 Collecting legal info
ERROR: COPYRIGHT.txt has wrong sha256 hash:
ERROR: expected: a85a622378c6a892ead1ce5d0488e446e106bf014d3b763fdbc1ad1ae38ee491
ERROR: got : 7b8dbd54ab1543b07b2fc5f6f5ab50d89d26c1c4952af93a579d8c52c56b8de4
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
make[1]: *** [package/supervisor/supervisor.mk:36: supervisor-legal-info] Error 1
make: *** [Makefile:84: _all] Error 2
Could you check what are the differences between the COPYRIGHT.txt in
the old version and in the new version, explain them in the commit log,
and update the hash ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-09-07 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 20:14 [Buildroot] [PATCH 1/1] package/supervisor: bump to version 3.4.0 sam at gpsm.co.uk
2019-09-07 21:25 ` Thomas Petazzoni [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=20190907232513.40485c7a@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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