From: Meng Li <Meng.Li@windriver.com>
To: meta-freescale@lists.yoctoproject.org
Cc: meng.li@windriver.com
Subject: [PATCH] fmlib: set precise BSD license
Date: Tue, 26 Apr 2022 17:17:42 +0800 [thread overview]
Message-ID: <20220426091742.14191-1-Meng.Li@windriver.com> (raw)
From: Meng Li <meng.li@windriver.com>
When building fmlib package based on Yocto 4.0, there is below
warning reported
WARNING: fmlib-git-r1 do_populate_lic: QA Issue: fmlib:
No generic license file exists for: BSD in any provider [license-exists]
Because "BSD" is ambiguous, and there is no corresponding license file
in COMMON_LICENSE_DIR directory. So, set precise BSD license to fix
this issue.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
---
recipes-dpaa/fmlib/fmlib_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-dpaa/fmlib/fmlib_git.bb b/recipes-dpaa/fmlib/fmlib_git.bb
index cad064f2..bf834c4b 100644
--- a/recipes-dpaa/fmlib/fmlib_git.bb
+++ b/recipes-dpaa/fmlib/fmlib_git.bb
@@ -1,6 +1,6 @@
DESCRIPTION = "Frame Manager User Space Library"
SECTION = "fman"
-LICENSE = "BSD & GPL-2.0-only"
+LICENSE = "BSD-3-Clause & GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=9c7bd5e45d066db084bdb3543d55b1ac"
PR = "r1"
--
2.17.1
reply other threads:[~2022-04-26 9:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220426091742.14191-1-Meng.Li@windriver.com \
--to=meng.li@windriver.com \
--cc=meta-freescale@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).