Hi, Please join us for the upcoming OpenEmbedded Happy Hour on April 28 for Asia/Pacific timezones @ 2100/9pm UTC (5pm EDT): https://www.openembedded.org/wiki/Calendar https://www.timeanddate.com/worl

Current Dev Position: YP 3.4 M1 Next Deadline: 7th June 2021 YP 3.4 M1 build Next Team Meetings: Bug Triage meeting Thursday Apr. 29th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bF

When I trying using bitbake to build openembedded Linux kernel, it dies with these download failures: NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/3.0/x86_

Hi All, I am trying to run my application in less privilege mode instead of root user. As i am new to Yocto build could you please some one suggest on how to configure my build environment to get user

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+ 11766 nobody group added by systemd sysusers.d randy

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 16 yf3yu@... 8 michael.opdenacker@... 3 mhalstead@... 2 randy.macleod@... 2 prabin.ca@.

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

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

Signed-off-by: Jon Mason <jon.mason@...> --- .gitlab-ci.yml | 172 ++++++++++++++++++++++++++++++++++++++ ci/96b-avenger96.yml | 9 ++ ci/96b-nitrogen.yml | 6 ++ ci/acrn.yml | 6 ++ ci/base.yml | 35 ++++

No one asked for it, but here it is, Gitlab CI for meta-zephyr. Stolen and repurposed from meta-arm. This building and testing should help discover regressions more quickly. And if you include this pa

From: Yann Dirson <yann@...> Changes in v4: - install our bsp files in bsp/rockchip/ rather than directly in bsp/ - also add "serial" to MACHINE_FEATURES Changes in v3: - relocate the bsp files into f

Hello community, I am looking for a best practice / a simple solution for switching the SRCREV in a bitbake recipe between git master HEAD (default, used in nightly builds) and a tagged release versio

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-security/libseccomp/files/run-ptest | 4 -- .../libseccomp/libseccomp_2.5.1.bb | 47 ------------------- 2 files changed, 51 deletions(-) delete

collect-data template can run arbitrary commands/scripts on a regular basis and logs the output in a file. See oe-core for more details: edb7098e9e buildstats.bbclass: add functionality to collect bui

I added a custom layer and under recipes-kernel I try to apply kernel config fragments: └[~]> cat poky/meta-insidem2m/recipes-kernel/linux/linux-yocto_5.10.bbappend FILESEXTRAPATHS_prepend := "${THISD

Ah, I forgot to put all of this in a bsp/rockchip/ dir, will reroll.

From: Yann Dirson <yann@...> Changes from v2: - turn the DISTRO_FEATURE idea into separate RFC patches so as to allow merging of basic support - remove optee-os patch that proved unnecessary Changes f

OE-Core rev: fd1c26ab426c3699ffd8082b83d65a84c8eb8bff added an additional parameter, tmpfsdir, to the API. This caused testimage to no longer work in meta-zephyr. Add that parameter and everything is

Signed-off-by: Armin Kuster <akuster808@...> --- ...Makefile-drop-running-scrips-install.patch | 37 +++ .../0002-Makefile-don-t-set-uid-gid.patch | 251 ++++++++++++++++++ recipes-ids/ossec/ossec-hids_

Hi Guys, I am newly facing this when I want to build core-image-sato image. how can I fix this issue can anybody know please suggest me. local.conf I enabled EXTRA_IMAGE_FEATURES += "staticdev-pkgs" b