From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 2/2] debootstrap: change license to MIT
Date: Sun, 19 Nov 2017 10:41:39 -0800 [thread overview]
Message-ID: <1511116899-6122-2-git-send-email-akuster808@gmail.com> (raw)
In-Reply-To: <1511116899-6122-1-git-send-email-akuster808@gmail.com>
The closest thing to a license is found in the http://metadata.ftp-master.debian.org/changelogs/main/d/debootstrap/debootstrap_1.0.92_copyright
The verbage looks very close to MIT so seems reasonable make to change the license to MIT instead of
creating a custom entry for debootstrap-custom-license. This follows what Redhat, Mandriva and Suse have for this package. (see rpmfind)
will fix: WARNING: debootstrap-1.0.67-r0 do_populate_lic: debootstrap: No generic license file exists for: debootstrap-custom-license in any provider
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
meta-oe/recipes-devtools/debootstrap/debootstrap_1.0.67.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-oe/recipes-devtools/debootstrap/debootstrap_1.0.67.bb b/meta-oe/recipes-devtools/debootstrap/debootstrap_1.0.67.bb
index 62b2796..8472aca 100644
--- a/meta-oe/recipes-devtools/debootstrap/debootstrap_1.0.67.bb
+++ b/meta-oe/recipes-devtools/debootstrap/debootstrap_1.0.67.bb
@@ -1,7 +1,7 @@
SUMMARY = "Install a Debian system into a subdirectory"
HOMEPAGE = "https://wiki.debian.org/Debootstrap"
SECTION = "devel"
-LICENSE = "debootstrap-custom-license"
+LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://debian/copyright;md5=1e68ced6e1689d4cd9dac75ff5225608"
inherit pkgconfig
--
2.7.4
next prev parent reply other threads:[~2017-11-19 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 18:41 [meta-oe][PATCH 1/2] UFL: add missing license Armin Kuster
2017-11-19 18:41 ` Armin Kuster [this message]
2017-11-19 19:06 ` [meta-oe][PATCH 2/2] debootstrap: change license to MIT Khem Raj
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=1511116899-6122-2-git-send-email-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.