Hi, I followed Yocto document 2.3.3 Changing the Configuration to set up a complete working Linux kernel defconfig in my kernel bbappend, I copied the defconfig to build/.config: do_compile:prepend

A build flagged for QA (yocto-3.1.16.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.16.rc1 Build hash information: bitbake:

The intent here is to use the latest release branch name instead of a tagged version. For the 4.0 case, this means the full migration guide will be shown instead of the reduced information in the 4.0

Hello, We, the German Linux magazine, are planning a focus on Linux distributions for the IoT in the 07/22 issue. One of them we have in mind is Yocto. We are therefore looking for an author who

Hi, I'm wondering if there is a mechanism I could utilize to create target directories in one place that is shared between recipes? I have an image that has multiple packages being created and

All, YP M+ or high bugs which moved to a new milestone in WW17 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 12272 Create new test cases for Kernel

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 40 bug owners as of the end of WW17 of who have open medium or higher bugs and enhancements against YP 4.1. There are 130 possible work days left until the final

oh, I see. thanks!

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

Merged, thanks.

Merged, thanks.

Hi Ross, I tried out the regex solution but I did not work and I also noticed that the 3.1.x doc versions on the documentation website already contains the banner I thought from 3.1.2 above were not

There has been a persistent stream of graphical failures on x32, and there is doubt about whether x32 is at all used by anyone nowadays - let's reduce the scope of x32 QA, and perhaps later drop it

From: Stefan Schmidt <stefan.schmidt@...> When running an up-to-date userspace component, like otbr-agent or ot-daemon, with Thread 1.2 enabled we need a firmware matching

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

Hello That's what you get when you use /bin/sh as the init process. Instead, you could use the normal init program built in your image (which one it is, Systemd or BusyBox init?), and get it to run

Hi Ross, To be fair, the list of impacted versions for dunfell is finite, since we're talking about old docs that aren't regenerated anymore. Dunfell was migrated to Sphinx (and is thus regenerated

The logging and re imports are unused, remove these. Add a comment explaining why you need to add a <div> wrapping the main content. Hardcoding numbers like this isn’t a great idea. If the

Hello Vasyl, can you explain how this was tested? Is it possible to automate with qemu targets? Alex <Vasyl.Vavrychuk@...> wrote: