Bug 8199 - Bitbake does not give incompatible license error on provided package
Summary: Bitbake does not give incompatible license error on provided package
Status: RESOLVED NOTABUG
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-08-21 22:20 UTC by Alan Olsen
Modified: 2015-08-24 10:31 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Olsen 2015-08-21 22:20:44 UTC 
We have the following set in localconf:

INCOMPATIBLE_LICENSE = "LGPLv3 GPLv3"

We have a build that contains a package that is provided by a meta yocto recipe that is not the main package. The build fails (as it should) but does not provide the error message giving the correct reason why it fails.

Reproducible test case:

If you build "bitbake gdb" with the above set, it will fail with the incompatible license violation.

If you build "bitbake gdbserver" it will claim it cannot find the package. gdbserver is provided by gdb.

If the gdbserver requirement is the first package seen with the license issue, it fails, but gives the wrong error.
Comment 1 Ross Burton 2015-08-24 10:31:37 UTC 
bitbake takes recipe names not package names, so "bitbake gdb" is the correct invocation and "bitbake gdbserver" is expected to fail.