Getting rid of "The license listed internal was not in the licenses collected" warnings?

Getting rid of "The license listed internal was not in the licenses collected" warnings?

[Mike Looijmans]

In my layer.conf I have:

LICENSE_PATH += "${LAYERDIR}/licenses"


In that path, there's a license file called "internal" containing the 
following short text:

For TOPIC internal use only.
Do not distribute.


Now on each build I get warnings like this for every recipe that refers to 
this license:
"WARNING: The license listed internal was not in the licenses collected for 
recipe ..."


As far as I know, I did everything right, but I can't figure out what else I 
need to do here. How do I get this license into the "license collected"?

Mike.


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

Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?

[Mike Looijmans]

Just sped another hour or so trying to pinpoint this, but I cannot wrap my 
head around it. What do I have to do to add a license to a layer without these 
annoying warnings?

Mike.


On 03-07-15 09:23, Mike Looijmans wrote:
> In my layer.conf I have:
>
> LICENSE_PATH += "${LAYERDIR}/licenses"
>
>
> In that path, there's a license file called "internal" containing the
> following short text:
>
> For TOPIC internal use only.
> Do not distribute.
>
>
> Now on each build I get warnings like this for every recipe that refers to
> this license:
> "WARNING: The license listed internal was not in the licenses collected for
> recipe ..."
>
>
> As far as I know, I did everything right, but I can't figure out what else I
> need to do here. How do I get this license into the "license collected"?
>




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

Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?

[Jussi Kukkonen]

[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]

On 7 September 2015 at 13:14, Mike Looijmans <mike.looijmans@topic.nl>
wrote:

> Just sped another hour or so trying to pinpoint this, but I cannot wrap my
> head around it. What do I have to do to add a license to a layer without
> these annoying warnings?


I just tried this (with master branch) and it seems to work fine here...
Are you using master or something older?

Do you not get a "${DEPLOY_DIR}/licenses/${BPN}/generic_internal" file when
you build the recipe for BPN?

 - Jussi


Mike.
>
>
> On 03-07-15 09:23, Mike Looijmans wrote:
>
>> In my layer.conf I have:
>>
>> LICENSE_PATH += "${LAYERDIR}/licenses"
>>
>>
>> In that path, there's a license file called "internal" containing the
>> following short text:
>>
>> For TOPIC internal use only.
>> Do not distribute.
>>
>>
>> Now on each build I get warnings like this for every recipe that refers to
>> this license:
>> "WARNING: The license listed internal was not in the licenses collected
>> for
>> recipe ..."
>>
>>
>> As far as I know, I did everything right, but I can't figure out what
>> else I
>> need to do here. How do I get this license into the "license collected"?
>>
>>
>
>
>
> 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
>
>
>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 3337 bytes --]

Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?

[Mike Looijmans]

On 07-09-15 13:56, Jussi Kukkonen wrote:
> On 7 September 2015 at 13:14, Mike Looijmans <mike.looijmans@topic.nl
> <mailto:mike.looijmans@topic.nl>> wrote:
>
>     Just sped another hour or so trying to pinpoint this, but I cannot
>     wrap my head around it. What do I have to do to add a license to a
>     layer without these annoying warnings?
>
>
> I just tried this (with master branch) and it seems to work fine
> here...  Are you using master or something older?

Did you try that in a separate, empty layer? I suspect I'm missing a 
variable or directive of some kind which cause it to miss the license file.

> Do you not get a "${DEPLOY_DIR}/licenses/${BPN}/generic_internal" file
> when you build the recipe for BPN?

Nope.


>
>   - Jussi
>
>     Mike.
>
>
>     On 03-07-15 09:23, Mike Looijmans wrote:
>
>         In my layer.conf I have:
>
>         LICENSE_PATH += "${LAYERDIR}/licenses"
>
>
>         In that path, there's a license file called "internal"
>         containing the
>         following short text:
>
>         For TOPIC internal use only.
>         Do not distribute.
>
>
>         Now on each build I get warnings like this for every recipe that
>         refers to
>         this license:
>         "WARNING: The license listed internal was not in the licenses
>         collected for
>         recipe ..."
>
>
>         As far as I know, I did everything right, but I can't figure out
>         what else I
>         need to do here. How do I get this license into the "license
>         collected"?
>
>
>
>
>
>     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
>     <tel:%2B31%20%280%29%20499%2033%2069%2079>
>     Telefax: +31 (0) 499 33 69 70 <tel:%2B31%20%280%29%20499%2033%2069%2070>
>     E-mail: mike.looijmans@topicproducts.com
>     <mailto:mike.looijmans@topicproducts.com>
>     Website: www.topicproducts.com <http://www.topicproducts.com>
>
>     Please consider the environment before printing this e-mail
>
>
>
>
>
>     --
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


-- 
Mike Looijmans

Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?

[Jussi Kukkonen]

[-- Attachment #1: Type: text/plain, Size: 2983 bytes --]

On 7 September 2015 at 19:38, Mike Looijmans <mike.looijmans@topic.nl>
wrote:

> On 07-09-15 13:56, Jussi Kukkonen wrote:
>
>> On 7 September 2015 at 13:14, Mike Looijmans <mike.looijmans@topic.nl
>> <mailto:mike.looijmans@topic.nl>> wrote:
>>
>>     Just sped another hour or so trying to pinpoint this, but I cannot
>>     wrap my head around it. What do I have to do to add a license to a
>>     layer without these annoying warnings?
>>
>>
>> I just tried this (with master branch) and it seems to work fine
>> here...  Are you using master or something older?
>>
>
> Did you try that in a separate, empty layer? I suspect I'm missing a
> variable or directive of some kind which cause it to miss the license file.
>

I have layer with literally only:
* conf/layer.conf file with just LICENSE_PATH += "${LAYERDIR}/licenses"
* licenses/internal file
This layer is added to BBLAYERS. After this a recipe from another layer
seems to be able to use the "internal" license...

Jussi


Do you not get a "${DEPLOY_DIR}/licenses/${BPN}/generic_internal" file
>> when you build the recipe for BPN?
>>
>
> Nope.
>
>
>
>>   - Jussi
>>
>>     Mike.
>>
>>
>>     On 03-07-15 09:23, Mike Looijmans wrote:
>>
>>         In my layer.conf I have:
>>
>>         LICENSE_PATH += "${LAYERDIR}/licenses"
>>
>>
>>         In that path, there's a license file called "internal"
>>         containing the
>>         following short text:
>>
>>         For TOPIC internal use only.
>>         Do not distribute.
>>
>>
>>         Now on each build I get warnings like this for every recipe that
>>         refers to
>>         this license:
>>         "WARNING: The license listed internal was not in the licenses
>>         collected for
>>         recipe ..."
>>
>>
>>         As far as I know, I did everything right, but I can't figure out
>>         what else I
>>         need to do here. How do I get this license into the "license
>>         collected"?
>>
>>
>>
>>
>>
>>     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
>>     <tel:%2B31%20%280%29%20499%2033%2069%2079>
>>     Telefax: +31 (0) 499 33 69 70
>> <tel:%2B31%20%280%29%20499%2033%2069%2070>
>>     E-mail: mike.looijmans@topicproducts.com
>>     <mailto:mike.looijmans@topicproducts.com>
>>     Website: www.topicproducts.com <http://www.topicproducts.com>
>>
>>     Please consider the environment before printing this e-mail
>>
>>
>>
>>
>>
>>     --
>>     _______________________________________________
>>     Openembedded-core mailing list
>>     Openembedded-core@lists.openembedded.org
>>     <mailto:Openembedded-core@lists.openembedded.org>
>>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>
>>
>
> --
> Mike Looijmans
>

[-- Attachment #2: Type: text/html, Size: 5644 bytes --]

Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?

[Mike Looijmans]

On 08-09-15 10:44, Jussi Kukkonen wrote:
> On 7 September 2015 at 19:38, Mike Looijmans <mike.looijmans@topic.nl
> <mailto:mike.looijmans@topic.nl>> wrote:
>
>     On 07-09-15 13:56, Jussi Kukkonen wrote:
>
>         On 7 September 2015 at 13:14, Mike Looijmans <mike.looijmans@topic.nl
>         <mailto:mike.looijmans@topic.nl>
>         <mailto:mike.looijmans@topic.nl <mailto:mike.looijmans@topic.nl>>> wrote:
>
>              Just sped another hour or so trying to pinpoint this, but I cannot
>              wrap my head around it. What do I have to do to add a license to a
>              layer without these annoying warnings?
>
>
>         I just tried this (with master branch) and it seems to work fine
>         here...  Are you using master or something older?
>
>
>     Did you try that in a separate, empty layer? I suspect I'm missing a
>     variable or directive of some kind which cause it to miss the license file.
>
>
> I have layer with literally only:
> * conf/layer.conf file with just LICENSE_PATH += "${LAYERDIR}/licenses"
> * licenses/internal file
> This layer is added to BBLAYERS. After this a recipe from another layer seems
> to be able to use the "internal" license...

The warning doesn't appear until you actually build a rootfs with that package 
in it.

>
>         Do you not get a "${DEPLOY_DIR}/licenses/${BPN}/generic_internal" file
>         when you build the recipe for BPN?
>
>
>     Nope.

Ah, wait, on closer inspection it actually exists, but it's a symlink to some 
none-existing location. Apparently, to save some diskspace and reduce 
maintenance on text files I linked a few files together. Somehow, the link got 
copied instead of the file contents.

I un-symlinked the "internal" file, and (together with some forced rebuilds) 
that finally made the warning go away.

Thanks!


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

Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?

[Mikko.Rapeli]

On Tue, Sep 08, 2015 at 12:19:51PM +0200, Mike Looijmans wrote:
> Ah, wait, on closer inspection it actually exists, but it's a symlink to
> some none-existing location. Apparently, to save some diskspace and reduce
> maintenance on text files I linked a few files together. Somehow, the link
> got copied instead of the file contents.
>
> I un-symlinked the "internal" file, and (together with some forced rebuilds)
> that finally made the warning go away.

Since I had similar stupid-user moments too, there is a generic function in
sanity tests to check for broken symlinks. Would be great if you could add
license files to this check.

-Mikko