All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: WARNING: The license listed CLOSED was not in the licenses collected for foo
Date: Fri, 08 May 2015 13:07:35 +0200	[thread overview]
Message-ID: <554C98F7.5090005@dresearch-fe.de> (raw)

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?

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058


             reply	other threads:[~2015-05-08 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 11:07 Steffen Sledz [this message]
2015-05-08 12:39 ` WARNING: The license listed CLOSED was not in the licenses collected for foo 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
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=554C98F7.5090005@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=openembedded-core@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.