From: <Mikko.Rapeli@bmw.de>
To: <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Getting rid of "The license listed internal was not in the licenses collected" warnings?
Date: Tue, 8 Sep 2015 10:39:46 +0000 [thread overview]
Message-ID: <20150908103552.GE8427@loska> (raw)
In-Reply-To: <55EEB647.7000101@topic.nl>
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
prev parent reply other threads:[~2015-09-08 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 7:23 Getting rid of "The license listed internal was not in the licenses collected" warnings? Mike Looijmans
2015-09-07 10:14 ` Mike Looijmans
2015-09-07 11:56 ` Jussi Kukkonen
2015-09-07 16:38 ` Mike Looijmans
2015-09-08 8:44 ` Jussi Kukkonen
2015-09-08 10:19 ` Mike Looijmans
2015-09-08 10:39 ` Mikko.Rapeli [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=20150908103552.GE8427@loska \
--to=mikko.rapeli@bmw.de \
--cc=mike.looijmans@topic.nl \
--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.