From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: poky@yoctoproject.org
Subject: Re: License warnings
Date: Tue, 08 Feb 2011 07:51:52 -0800 [thread overview]
Message-ID: <4D516698.1060703@intel.com> (raw)
In-Reply-To: <4D514B12.2080301@mlbassoc.com>
On 02/08/2011 05:54 AM, Gary Thomas wrote:
> I just noticed some warnings since I updated to master
> from 2011-02-03 (0fdcc509c534d4e561674be02d26efedf638f7c6)
>
> ---------------- WARNINGS ---------------------------------
> WARNING: bind: Something went wrong with copying: ISC to /home/local/poky-amltd/meta/files/common-licenses
> WARNING: This could be either because we do not have a generic for this license or the LICENSE field is incorrect
>
> WARNING: sqlite3: Something went wrong with copying: PD to /home/local/poky-amltd/meta/files/common-licenses
> WARNING: This could be either because we do not have a generic for this license or the LICENSE field is incorrect
>
> WARNING: db: Something went wrong with copying: Sleepycat to /home/local/poky-amltd/meta/files/common-licenses
> WARNING: This could be either because we do not have a generic for this license or the LICENSE field is incorrect
> ---------------- WARNINGS ---------------------------------
>
> Should I be concerned? Is there something to fix here?
>
Not really. This is just a warning that the license listed in the recipe
does not have a generic that it could find to copy over to the license
wrangling directory. ISC, PD and Sleepycat all wouldn't have generics
yet, so nothing to worry about.
-b
------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
prev parent reply other threads:[~2011-02-08 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 13:54 License warnings Gary Thomas
2011-02-08 15:51 ` Elizabeth Flanagan [this message]
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=4D516698.1060703@intel.com \
--to=elizabeth.flanagan@intel.com \
--cc=poky@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 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.