Hi all I'd like to install my python3 application in a custom folder with all local packages and data. The source code folder has this

I got a question about the linux-firmware-bcm4373 package. The link /lib/firmware/brcm/brcmfmac4373-sdio.clm_blob -> ../cypress/cyfmac4373-sdio.clm_blob is packaged into linux-firmware and not into

I think the best way out for you is to set up a container with a supported older distribution. Usually you need an older gcc version from the host machine, so the container will have that. Alex

Hi, Has anyone tried to build yocto 2.6 on Ubuntu 20.04? I know it's not supported, but it's a major task for me to upgrade to yocto 3.x. I tried it myself and it fails on building qemu-native. I

Hello, so I'm a bit at a loss. I admit, I've not yet been using Yocto for a long time. I'm trying to use base-utils as provided by packagegroup-core-base-utils to have a more full featured set of base

Hi, Please don't include CVE twice in the variable name, that's was annoying and just got used to the CVE_CHECK_WHITELIST one. CVE_CHECK_IGNORE would do. Cheers, -Mikko

Hi Michael, One change at a time please ☺️ This should be done right after the git checkout. It's better to ensure what you build is clean that try to ensure the next oneto build has a clean

Hello All, Advice on working with Yocto and Raspberry Pi CM4 Lite would be helpful.I recently got my hands on with CM4 and now I want to build Yocto image with u-boot as bootloader. I have few

I am trying to fetch a private gitlab repo within Yocto image recipe using SSH protocol. In my image recipe I have passed SRC_URI as: SRC_URI = " \

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.5_M2.rc6. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

The layer index does already support this, it's just not exposed (at the time I introduced it - some time ago - I thought it might encourage people to deviate from the release branch names, but in

Hi folks I've been looking into a couple of compiler flags for hardening that I think we might want to consider enabling by default in security-flags.inc: 1) -fstack-clash-protection This option

Once a week has proven a bit too hectic: it's better to have more time to test, submit, review and integrate the updates before AUH runs again. Signed-off-by: Alexander Kanavin

Jon, I've looked over all the changes and agree with Ross on his one suggestion and that the rest of the changes are fine. The new terms are equally or in some cases more clear so hopefully that

All, Our next OpenEmbedded Happy Hour is on January 26 for Europe/Americas timezones @ 1700/5pm UTC (12pm ET / 9am

The idea is we're trying to use the language which makes sense and "devel" says what the branch is/does. Cheers, Richard

A wrong path was given given the working directory. Also revert the changes with "git reset --hard" to have a clean state before further branch switches. Signed-off-by: Michael Opdenacker

This is the only one that sticks out to me. I think it needs another _, SKIP_RECIPE and IGNORE_CVE. Other than that, +1. Will we have a bit of logic to detect the obsolete names being set and emit

Personally, the only advantage of 'main' is muscle memory of m[tab]. Semantically it's not the 'main' branch, it's the active development branch. Thus, devel. Ross

Current Dev Position: YP 3.5 M3 Next Deadline: 21th Feb. 2022 YP 3.5 M3 build Next Team Meetings: Bug Triage meeting Thursday Jan. 27th 7:30 am PDT