Hellow everyone, this is Yan. I am new to Yocto Project, still, I am learning. There is a question, when I bitbaked my image I found this ERROR: yanxk@yanxk-Ubuntu:~/Yocto/poky/build$ bitbake core-ima

From: Mingli Yu <mingli.yu@...> Fixes: WARNING: samhain-standalone-4.4.9-r0 do_package_qa: QA Issue: File /usr/share/doc/samhain-standalone/scripts/samhain.ebuild-light in package samhain-standalone-d

From: John Edward Broadbent <jebr@...> Generic Low Overhead Message Exchange (GLOME) is a protocol providing secure authentication and authorization for low dependency environments. Signed-off-by: Joh

Fix error as the fowllowing: resource-agents-4.5.0-r0 do_package_qa: QA Issue: lib32-resource-agents installs files in /var/volatile, but it is expected to be empty [empty-dirs] Signed-off-by: Lei Mao

Hi all, I have taken on myself a task to write a custom Yocto-based image for Nvidia Xavier which poses somewhat of a difficult task. After few videos on Youtube and some documentation, I started writ

The changes to split classes into global vs. image specific contexts has broken the inclusion of `wine` and `wineserver` host tools for testing MinGW SDKs. This is because testsdk is an image specific

it is part of systemd recipe if your distro is based on systemd. In that case, you can write a bbappend where you define do_install:append() and delete it from staging area before it gets packaged

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Steve Sakoman, Joshua Watt, Randy Macleod, Richard Purdie, Aryaman, Bruce Ashfield, Michael Opdenacker, Alexandre Belloni, Pavel Zhukov,

Hello, I am aware of a new build failure with suricata. I think it related to the glibc update. https://errors.yoctoproject.org/Errors/Build/150774/ I will have limited time to look into this in the n

Hello all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.0.3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2

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

Good Afternoon, I am updating a project from Honister to Kirkstone, Has anyone else run into an issue with python files with a #!/usr/bin/python header throwing the (abbreviated) Error below? This did

Howdy there! We're happy to finally announce the Yocto Project Mini-Summit taking place the day before ELC-E in Dublin! Monday, September 12th, 2022 | 2:00 – 5:30 PM Location: Convention Centre Dublin

Hi, For a firewall recipe using nftables we need to make some kernel configuration changes. At first we added the needed CONFIG_ lines to a bbappend in the recipes-kernel directory of our own layer, b

Hi Since the last version of bibake it looks like SRCREV must be set with a SHA1 in order to fetch source from a git repository. We previously set it with a tag corresponding to PV. Manually retrievin

Hello: I built kirkstone core-image-sato from scratch no modifications, clean build was going test kirkstone out… When I went to run using qemu I saw the following issue with “tun”, even after a manua

Current Dev Position: YP 4.1 M3 Next Deadline: 22nd August 2022 YP 4.1 M3 Build Next Team Meetings: Bug Triage meeting Thursday August 11th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 1 randy.macleod@... 1 Grand Total 2 Thanks, Stephen K. Jolley Yocto Project Program Man

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

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 the