From: Peter Hoyes <Peter.Hoyes@...> Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- ci/base.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/ci/base.yml b/ci/base.yml index

From: Peter Hoyes <Peter.Hoyes@...> Hello World and Philosophers do not have a SUMMARY or DESCRIPTION, so add these to both recipes. Signed-off-by: Peter Hoyes <Peter.Hoyes@...> ---

From: Peter Hoyes <Peter.Hoyes@...> The Zephyr documentation [1] lists 3 "classic samples" that "can be run on any of the supported platforms": Hello World, Synchronization and Dining

Hello Naveen, They have worked for a few days now, but were broken for the previous 2-3 weeks. You can see all the zephyr machines in meta-arm failed 4 days

Greetings ! I have compiled yocto for i.MX6UL (Zeus) . Can anyone help me out with the exact procedure to add Docker along with its required dependency packages to Yocto build. I tried cloning

A patch to address this would be appreciated. Alex

This is where we should perhaps think about the filter variable option Joshua and I have talked about periodically as that could handle this in a much neater and generic way, at the unfortunate cost

You can use VIRTUAL-RUNTIME_sed variable instead of 'sed' _everywhere_ and then change the preferred runtime provider in your DISTRO config. Similar case for "stat" from busybox in webOS

I have a recipe which contains a script that uses /bin/sed. When I build it, I get an error: ERROR: myrecipe-1.2.3-r0 do_package_qa: QA Issue: /lib/myrecipe/mycommand contained in package myrecipe

My local daily builds also run on master. I triggered a kirkstone build today, it builds successfully for me. Is it failing for specific machine ?

I've recently been upgrading from dunfell to kirkstone. I see a regression in the resolvconf package, so DNS lookups aren't functional. I see in /var/log/messages: Aug 2 19:39:31 tv999996 daemon.warn

Hello We are pleased to announce the Yocto Project 3.1.18 (dunfell-23.0.18) Release is now available for

0.7 - that's pre-dunfell! For master or kirkstone, see: https://lists.yoctoproject.org/g/linux-yocto/message/11523?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Cmacleod%2C20%2C1%2C0%2C92659340 and

Greetings 5 videos from Yocto Project talks at the Embedded Linux Conference North America are now available on YouTube: BoF: The Yocto Project and OpenEmbedded Organization - Philip Balister,

Hi Joshua, It's 100% my fault, I'm mixed 2 variables: ROOTFS_POSTPROCESS_COMMAND IMAGE_POSTPROCESS_COMMAND My "ln " command have to be placed into IMAGE_POSTPROCESS_COMMAND, not

Yes! We have a patch under review for kirkstone: https://lists.openembedded.org/g/openembedded-core/message/168636 I think Richard is hoping someone will see if that also will work on master and if

The autotest change allows for the list of targets to be built to be larger. Add more targets to increase the build coverage of CI. Unfortunately, there are some platforms that do not build

Trivial change to move stm32mp157c-dk2 to its alphabetical location. This is relevant because it aligns the file to match the order on the gilab pipeline entry. Signed-off-by: Jon Mason

Warnings are being seen in gitlab of WARNING - Falling back to file-relative addressing of local include "base.yml" WARNING - Update your layer to repo-relative addressing to avoid this warning

From: Peter Hoyes <Peter.Hoyes@...> When TESTIMAGE_AUTO is enabled, the do_testimage task is inserted after do_image_complete and before do_build so that the test suites automatically run as part