From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] libyaml: fix libyaml-legal-info build failure
Date: Wed, 29 Aug 2018 21:23:19 +0300 [thread overview]
Message-ID: <87zhx5vxpk.fsf@tkos.co.il> (raw)
In-Reply-To: <20180829173320.66826-1-giulio.benetti@micronovasrl.com>
Hi Giulio,
Giulio Benetti writes:
> LICENSE file hash is wrong, this leads to libyaml-legal-info build
> failure. This is probably due to version bump.
What are the changes in the LICENSE file in this version bump? Does it
affect the license? Please mention these details in the commit log.
baruch
> Recalculate it locally and substitute it in libyaml.hash file.
>
> Fixes:
> http://autobuild.buildroot.net/results/c10/c10baf6e9bae92d515264b677eeb1ce6c98c793d//
> http://autobuild.buildroot.net/results/c66/c66ddb56fecf1570a8669bd9d8824cd2132f9776//
> http://autobuild.buildroot.net/results/84e/84e9530aff0c981a009416f31470133fb2114421//
>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
> package/libyaml/libyaml.hash | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/libyaml/libyaml.hash b/package/libyaml/libyaml.hash
> index 755ea7bbd8..afc014dfb2 100644
> --- a/package/libyaml/libyaml.hash
> +++ b/package/libyaml/libyaml.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> sha256 78281145641a080fb32d6e7a87b9c0664d611dcb4d542e90baf731f51cbb59cd yaml-0.2.1.tar.gz
> -sha256 d0d8b09800a45cd982e9568fc7669d9c1a4c330e275a821bbe24d54366d16fe9 LICENSE
> +sha256 bfcb6a7dfbfd30e0ccc8bb34ab712bd1568586ad8c5b078ccae443b04e79749e LICENSE
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2018-08-29 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 17:33 [Buildroot] [PATCH next] libyaml: fix libyaml-legal-info build failure Giulio Benetti
2018-08-29 18:23 ` Baruch Siach [this message]
2018-08-29 18:29 ` Giulio Benetti
2018-08-29 18:36 ` [Buildroot] [PATCH next v2] " Giulio Benetti
2018-08-29 18:57 ` Thomas Petazzoni
2018-08-29 19:51 ` Giulio Benetti
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=87zhx5vxpk.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--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