Use convert-spdx-licenses.py to update LICENSE names in recipes. Signed-off-by: Joe Slater <joe.slater@...> --- recipes-security/refpolicy/refpolicy_common.inc | 2 +-

I was building esdk using Honister release and added a single package (using IMAGE_INSTALL), providing a library. As per documentation, target Sysroot must contain all the libraries and header files

Use convert-spdx-licenses.py to update LICENSE in recipes. Signed-off-by: Joe Slater <joe.slater@...> --- meta-security-compliance/recipes-auditors/lynis/lynis_3.0.0.bb | 2 +-

I have added the include file and compiled it. But same errors observed with few more errors. These errors are observed in the stage of bitbake linux-qoriq-rt -c configure. Also, found following notes

It is better to use [include file](https://github.com/Freescale/meta-freescale/blob/dunfell/recipes-kernel/linux/linux-qoriq.inc) in similar way

Hello, I was trying to build a kernel for layerscape ls1046ardb setup. I referred the meta-freescale/recipes-kernel/linux/linux-qoriq_5.4.bb file from dunfell branch. Build configuration: Yocto

Hi When you want to use another version of the kernel it is better to create new recipe (.bb file). You could use existing linux-qoriq_5.10 [1] recipe as example, just change the SRC_URI, SRCREV

Hi Richard,

Hi, The default Linux kernel is built by using bitbake fsl-image-networking. Here, the kernel is built from meta-freescale/recipes-kernel/linux/linux-qoriq_5.4.bb path and source code is fetching from

Hi there, This is for meta-security and not for meta-selinux. Also for the master branch. corrected labels and sent another patch for the meta-security master branch. Please ignore this

Thanks!  14779 means we'll need an rc2. Do you have any information on whether 14782/14783 also occur in qemu images or are they just on the nuc hardware? Do you know if anyone is looking into them

It seems below change done manually and so LICENSE variable modified from GPLv2 to GPL-2.0-or-later. But it should be GPL-2.0-only Link:

It seems below change done manually and so LICENSE variable modified from GPLv2 to GPL-2.0-or-later. But it should be GPL-2.0-only Link:

Hi all, This is the full report for yocto-4.0.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone

Hello, I've already noticed this behaviour on dunfell and I have a reproducer: ninvaders.inc: --- DESCRIPTION = "Space invaders clone based on nCurses" HOMEPAGE =

Current Dev Position: YP 4.0 rc2 Next Deadline: 29th April 2022 YP 4.0 final release Next Team Meetings: Bug Triage meeting Thursday Apr.14th 7:30 am PDT

Thank you so much! That was the problem!

I've ended up removing the wrong arch binaries and ignoring the stripped ones. Unfortunately I have no idea on where to start to rebuild the binaries using the cross toolchain, everything seems to be

Can you reproduce this against something in OE-Core which has a similar set of patches? We really need to be able to reproduce the problem. Cheers, Richard

I think that I am not allowed to publish the code, but I can try to explain what I have done. 1. There were in total 8 patches before I started to work 2. Run: devtool modify linux-ttc 3. I applied