Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: WARNING: The license listed CLOSED was not in the licenses collected for foo
Date: Mon, 11 May 2015 11:39:18 +0200	[thread overview]
Message-ID: <555078C6.8060504@topic.nl> (raw)
In-Reply-To: <3739437.GgmXEBs0pQ@peggleto-mobl.ger.corp.intel.com>

On 11-05-15 11:36, Paul Eggleton wrote:
> At a guess, maybe do_populate_lic didn't re-execute for this recipe. Does it
> still happen if you bitbake -c cleansstate the recipe and try again?

Yes, it even complains about this on a completely fresh build.

>
> Cheers,
> Paul
>
> On Monday 11 May 2015 10:58:07 Mike Looijmans wrote:
>> Hmm, I cannot figure it out... I have in a recipe:
>>
>> LICENSE = "internal"
>> LIC_FILES_CHKSUM = "file://LICENSE;md5=cf85de037de7ae12cc2d0059741fdbae"
>>
>> Then in my layer.conf:
>>
>> LICENSE_PATH += "${LAYERDIR}/licenses"
>>
>> I have a file called "internal" in that path. Still, I get:
>>
>> WARNING: log_check: WARNING: The license listed internal was not in the
>> licenses collected for ...
>>
>> What am I missing still then? What does the warning mean? I thought I got
>> everything right, but either the licensing rules have changed or I never got
>> it right in the first place and a check was added to make me aware of that.
>> On 11-05-15 08:54, Mike Looijmans wrote:
>>> What is one expected to do when one justs wants to add the missing license
>>> to the "licenses collected for ..."?
>>>
>>> I'm a bit spoiled now, most OE messages explain what it expects me to do
>>> to
>>> fix the problem.
>>
>> Kind regards,
>>
>> Mike Looijmans
>> System Expert
>>
>> TOPIC Embedded Products
>> Eindhovenseweg 32-C, NL-5683 KH Best
>> Postbus 440, NL-5680 AK Best
>> Telefoon: +31 (0) 499 33 69 79
>> Telefax: +31 (0) 499 33 69 70
>> E-mail: mike.looijmans@topicproducts.com
>> Website: www.topicproducts.com
>>
>> Please consider the environment before printing this e-mail
>



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail







  reply	other threads:[~2015-05-11  9:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 11:07 WARNING: The license listed CLOSED was not in the licenses collected for foo Steffen Sledz
2015-05-08 12:39 ` Paul Eggleton
2015-05-08 12:40   ` Otavio Salvador
2015-05-08 12:47     ` Paul Eggleton
2015-05-11  6:54   ` Mike Looijmans
2015-05-11  8:58     ` Mike Looijmans
2015-05-11  9:36       ` Paul Eggleton
2015-05-11  9:39         ` Mike Looijmans [this message]
2015-05-11  9:09     ` Paul Eggleton
2015-05-12  6:03       ` Mike Looijmans
2015-05-13 10:59   ` Steffen Sledz

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=555078C6.8060504@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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