Hi Jupiter, I've had numerous issues in the past with codeaurora being down or extremely slow, so I wouldn't be surprised if that was a network blip of some kind. If it happens reliably in Yocto but

Hi TSC, This build of 3.4.4 had some issues on the autobuilder: * qemux86-64 ptest failure in lttng-tools - known issue https://bugzilla.yoctoproject.org/show_bug.cgi?id=14263

I was able to build u-boot-imx-2021.04-r0 in honister branch, but could not build it in kirkstone branch, here is the error message: ERROR: u-boot-imx-2021.04-r0 do_fetch: Fetcher failure: Fetch

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

Hi Quentin

I'm not sure it would. Shared state works by computing inputs into a checksum and then using that checksum to access the cache. Finding a "previous version" or a history to compare to therefore isn't

I'm not sure where to get a status on meta-selinux officially released branch with kirkstone support, I'm hoping this is the right place. I see it has been added to main but is it planned to be

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.15 to the latest korg -stable release that comprises the following commits: 45451e8015a9 Linux 5.15.36 bb906d15a99e

Current Dev Position: YP 4.1 M1 Next Deadline: 30th May 2022 YP 4.1 M1 Build Next Team Meetings: Yocto Project Summit - 17th-19th May (https://www.yoctoproject.org/yocto-project-summit-2022-05/) Bug

I have enabled those options in Busybox to no avail. I still cant see my files : # touch 1Чернаяг # ls -l 1Чернаяг -rw-r--r-- 1 root root 0 May 3 13:35

All, YP M+ or high bugs which moved to a new milestone in WW18 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 14065 Automated ptest regression

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macleod@... 6 ross.burton@... 2 akuster808@... 2 mhalstead@... 1 Grand

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

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

^ This line what is causing your error, remove it. With pam in DISTRO_FEATURES the required packages will get pulled in via dependencies. If you specify INIT_MANAGER = "systemd", then you do not

pam is a DISTRO_FEATURE as below, not a package as you've added above. -- Jack Mitchell, Consultant https://www.tuxable.co.uk

Apparently, this is not enough: bitbake core-image-weston /usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__

Hi Amahnui, On 4/27/22 19:27, Abongwa Amahnui Bonalais wrote:> Signed-off-by: Abongwa Bonalais Amahnui <abongwabonalais@...>> --- Adding a comment in the commit log to explain why this patch

Is your file created with the wrong name or is it actually just the 'ls' output that doesn't support unicode characters? If you're using busybox, I think these configuration options could be of

Signed-off-by: Steve Sakoman <steve@...> --- schedulers.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/schedulers.py b/schedulers.py index d21c6bb..c0a4261