From: Angelo Compagnucci <angelo@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/mono> fixing licenses hashes
Date: Tue, 5 Jun 2018 11:11:08 +0200 [thread overview]
Message-ID: <1528189868-4119-1-git-send-email-angelo@amarulasolutions.com> (raw)
This patch adds hashes for the licensing files and removes a file
no more present.
Fixes:
http://autobuild.buildroot.net/results/c69e55a3f7539ff65aaf57c96f52ebea7e456e48/
Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
---
package/mono/mono.hash | 3 +++
package/mono/mono.mk | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/package/mono/mono.hash b/package/mono/mono.hash
index 47e3442..2cde7b6 100644
--- a/package/mono/mono.hash
+++ b/package/mono/mono.hash
@@ -1,2 +1,5 @@
# sha256 locally computed
sha256 f0636baa0c1399805526142e799cb697ddccf736e506cf1a30a870eaa2830a89 mono-5.12.0.226.tar.bz2
+sha256 3b40a54878b5ac2767a764bd082f8772ab27c03b9da9c7328c4c4935725556f7 LICENSE
+sha256 fc488f3ec9f36856bea8cce5cdde1449176341ef93a3962b691970f8981799f4 mcs/COPYING
+sha256 2c3c3ef532828bcd42bb3127349625a25291ff5ae7e6f8d42e0fe9b5be836a99 external/Newtonsoft.Json/Tools/7-zip/copying.txt
diff --git a/package/mono/mono.mk b/package/mono/mono.mk
index 2d60fc6..d1fe9bb 100644
--- a/package/mono/mono.mk
+++ b/package/mono/mono.mk
@@ -8,7 +8,7 @@ MONO_VERSION = 5.12.0.226
MONO_SITE = http://download.mono-project.com/sources/mono
MONO_SOURCE = mono-$(MONO_VERSION).tar.bz2
MONO_LICENSE = GPL-2.0 or MIT (compiler, tools), MIT (libs) or commercial
-MONO_LICENSE_FILES = LICENSE mcs/COPYING eglib/COPYING \
+MONO_LICENSE_FILES = LICENSE mcs/COPYING \
external/Newtonsoft.Json/Tools/7-zip/copying.txt
MONO_INSTALL_STAGING = YES
--
2.7.4
next reply other threads:[~2018-06-05 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 9:11 Angelo Compagnucci [this message]
2018-06-05 16:43 ` [Buildroot] [PATCH] package/mono> fixing licenses 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=1528189868-4119-1-git-send-email-angelo@amarulasolutions.com \
--to=angelo@amarulasolutions.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