From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/3] qt5serialbus: fix 5.6.3 license file hashes
Date: Tue, 9 Oct 2018 09:46:53 +0200 [thread overview]
Message-ID: <20181009094653.5d4a6849@windsurf> (raw)
In-Reply-To: <20181002211637.2356-2-ps.report@gmx.net>
Hello,
On Tue, 2 Oct 2018 23:16:36 +0200, Peter Seiderer wrote:
> Fixes [1]:
>
> ERROR: LICENSE.FDL has wrong sha256 hash:
> ERROR: expected: ed8742a95cb9db653a09b050e27ccff5e67ba69c14aa2c3137f2a4e1892f6c0d
> ERROR: got : f827ad079686ba92cc94811e35492d0e8966f704008b6da9eeda0b659fb58a8d
>
> [1] http://autobuild.buildroot.net/results/f8dba48bc1e71332f3983e78c40989e5f864abf3
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/qt5/qt5serialbus/5.6.3/qt5serialbus.hash | 5 +++++
> 1 file changed, 5 insertions(+)
> create mode 100644 package/qt5/qt5serialbus/5.6.3/qt5serialbus.hash
Applied to master, thanks. I did a follow-up commit to move the 5.11.2
hashes to a per version hash file. I think we should do this for all
Qt5 modules.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-09 7:46 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 [this message]
2018-10-02 21:16 ` [Buildroot] [PATCH v1 3/3] qt5serialport: " Peter Seiderer
2018-10-09 7:47 ` Thomas Petazzoni
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=20181009094653.5d4a6849@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