From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 3/3] qt5serialport: fix 5.6.3 license file hashes
Date: Tue, 9 Oct 2018 09:47:09 +0200 [thread overview]
Message-ID: <20181009094709.605b6eb5@windsurf> (raw)
In-Reply-To: <20181002211637.2356-3-ps.report@gmx.net>
Hello,
On Tue, 2 Oct 2018 23:16:37 +0200, Peter Seiderer wrote:
> Fixes [1]:
>
> ERROR: LICENSE.FDL has wrong sha256 hash:
> ERROR: expected: ed8742a95cb9db653a09b050e27ccff5e67ba69c14aa2c3137f2a4e1892f6c0d
> ERROR: got : e1251235ce9853eecfecfa905da9ee29e9b76e4db2a1c9c4a20699f460419b08
>
> [1] http://autobuild.buildroot.net/results/320db38e94d68b2ea4451c3cc0bd7742c125cedb
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/qt5/qt5serialport/5.6.3/qt5serialport.hash | 7 +++++++
> package/qt5/qt5serialport/qt5serialport.hash | 5 -----
> 2 files changed, 7 insertions(+), 5 deletions(-)
> create mode 100644 package/qt5/qt5serialport/5.6.3/qt5serialport.hash
Applied to master, I also split the hashes of the 5.11.2 license files
in a separate hash file. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-09 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 21:16 [Buildroot] [PATCH v1 1/3] qt5connectivity: add license files hashes Peter Seiderer
2018-10-02 21:16 ` [Buildroot] [PATCH v1 2/3] qt5serialbus: fix 5.6.3 license file hashes Peter Seiderer
2018-10-03 4:52 ` Baruch Siach
2018-10-03 12:49 ` Thomas Petazzoni
2018-10-05 16:09 ` Yann E. MORIN
2018-10-09 7:46 ` Thomas Petazzoni
2018-10-02 21:16 ` [Buildroot] [PATCH v1 3/3] qt5serialport: " Peter Seiderer
2018-10-09 7:47 ` Thomas Petazzoni [this message]
2018-10-09 7:19 ` [Buildroot] [PATCH v1 1/3] qt5connectivity: add license files hashes Thomas Petazzoni
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=20181009094709.605b6eb5@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 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.