You can add a layer which will set LAYERSERIES_COMPAT for another layer, but it needs to be parsed before the layer you want to change,

Hi, have an issue with a layer which doesn't have the current dunfell release in it's LAYERSERIES_COMPAT_ -> can I overwrite it somehow in a different layer or local.conf? -> can I configure the error

i suspected it was a WR thing, thanks. rday

Is it possible to continue to add ptest for python-XX in the old way at present, and wait for the new recipe to be integrated (uncertain time), and then uniformly process the output? Or suspend the

I like the idea of format the output at level of pytest, in OEQA there is OETestResult class that is where the changes need to be made to add the option to use AM

To me this seems like Wind River's special sauce. The CHANGELOG in meta-intel says this: Added QEMU support. ------------------- We now build several virtio drivers into the kernel by default,

currently poring over wind river docs and in release notes for WR LTS 19 (equivalent to YP 3.0), one of the notes for RCPL 7 for this release of WR states: "New support to deploy a platform project

Hi, I am cross compile nodejs 12.16 recipe for ARM v7 target using Yocto 2.2. I can built nodejs as a individual task (i.e. bitbake -c compile) (with some changes in recipe) with dependency over

Op 03-05-2020 om 13:42 schreef Gmane Admin: Self answering, I added this to my image recipe: ROOTFS_POSTPROCESS_COMMAND += "install_initrd; " install_initrd() { bbnote "Adding initrd to image

Awesome. I endorse a pypi recipe shipping that, which recipes can then re-use. The next question is how to integrate that runner with pytest. Ross

It's packaged on pypi: https://pypi.org/project/betatest/ I need to do a new release as I tidied a few things up and added a subtest wrapper after I published v0.1.0. This gives me a kick to get that

Yes, this, please. I endorsed this approach on the oe-devel list when this first came up, and I'm really pleased you already implemented it. We could have a recipe in oe-core with this in, or just

Hi Raj, you seem to have been spot on. After adding the "packagegroup-core-full-cmdline" to my image all command output looks perfect. This packagegroup was the only relevant difference between

Another option could be to generate the output in the correct format directly from Python using something like this module which I wrote a few years

Is it possible to process the output directly, rather than tweak it via sed/awk shell pipelines that are very difficult to read? Alex

Thanks for the tip Rudolf! I found out that gpg has a --homedir flag to do the obvious. Since gpg builds a database, I cannot simply copy the key. Knowing that now, I can just create the gpg database

Because there are quite a few OSS that use pytest for testing, and the test output of pytest is not consistent with the output format of automake, so the output of pytest needs to be processed. The

Hi, I have a following statement to remove a node in a DTS file: &gpmi { /delete-node/ fsl,use-minimum-ecc; }; I can build it correctly in OpenWRT build, but I cannot built it correctly in OE /

Hello all, This is the full QA report for yocto-3.0.3.rc2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No

Hi, I ha a configuration for raspberry pi from recent dunfell branch. When I run my image with runquemu: [zork@archdevel yocto-wallscreen-qemu-build]$ runqemu runqemu - INFO - Running bitbake -e