From: Mike Looijmans <mike.looijmans@topic.nl>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
Steffen Sledz <sledz@dresearch-fe.de>
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 08:54:25 +0200 [thread overview]
Message-ID: <55505221.7030002@topic.nl> (raw)
In-Reply-To: <2224585.tBn3dhReiF@peggleto-mobl.ger.corp.intel.com>
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.
M.
On 08-05-15 14:39, Paul Eggleton wrote:
> Hi Steffen,
>
> On Friday 08 May 2015 13:07:35 Steffen Sledz wrote:
>> Since switching from dizzy to fido we've some warnings related to some of
>> our own closed source packages.
>>
>> WARNING: log_check: There is a warn message in the logfile
>> WARNING: log_check: Matched keyword: [WARNING:]
>> WARNING: log_check: WARNING: The license listed CLOSED was not in the
>> licenses collected for foo
>>
>> The recipes contain lines like this one:
>>
>> LICENSE = "CLOSED"
>>
>> How should we fix the recipe to avoid the warning?
>
> I think the part of the code that produces this warning probably should be
> ignoring the CLOSED value. Can I ask you to please file a bug? Feel free to add
> me on CC.
>
> Cheers,
> Paul
>
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
next prev parent reply other threads:[~2015-05-11 6:54 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 [this message]
2015-05-11 8:58 ` Mike Looijmans
2015-05-11 9:36 ` Paul Eggleton
2015-05-11 9:39 ` Mike Looijmans
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=55505221.7030002@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=sledz@dresearch-fe.de \
/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