On Wed, Mar 28, 2018 at 07:00:17PM +0300, Fathi Boudra wrote:
On 28 March 2018 at 18:55, Dan Rue dan.rue@linaro.org wrote:
On Wed, Mar 28, 2018 at 08:12:36AM +0300, Fathi Boudra wrote:
On 27 March 2018 at 21:12, Dan Rue dan.rue@linaro.org wrote:
On Tue, Mar 27, 2018 at 08:40:17PM +0300, Fathi Boudra wrote:
On 27 March 2018 at 20:08, Dan Rue dan.rue@linaro.org wrote:
I'm seeing this LIC_FILES_CHKSUM error on all the RC builds today.
Thanks Dan. Fixed in https://github.com/96boards/meta-rpb/commit/615072f03d49f71e88620e337f5ddd10...
Thanks for jumping on it. Is it possible to help me understand why OE keeps things like checksums for license files hard coded in recipes?
It's a requirement in writing a recipe: https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-rec... https://www.yoctoproject.org/docs/2.4.1/ref-manual/ref-manual.html#var-LIC_F...
It makes some sense - ensure you know what license you are building. What I still don't understand, is, why the license changing on the -next branch impacted the 4.4, 4.9, etc builds? I would have expected it to look in the source tree that it's building for its license, not, some other tree.
We ship multiple kselftests in the images:
- in-kernel
- mainline
- next
Since -next is always shipped, it affected all the builds, independently of the kernel used (4.4 or 4.9 or 4.14, etc...)
Ah. Thanks again.
Dan