Many layers append BBFILE_COLLECTIONS and therefore have 'core <layer>' During update.py, this means we are likely not handling the collection we expect: WARNING: /opt/workdir/git___git_openembedded_o

ERROR: Variable BB_ENV_EXTRAWHITE has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS ERROR: Variable BB_ENV_EXTRAWHITE from the shell environment has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS ERROR:

Add the newish Inactive-Upstream upstream status. Add 0046_alter_patch_status.py migration. Signed-off-by: Tim Orling <tim.orling@...> layerindex/migrations: update patch status Signed-off-by: Tim Orl

The url pattern was not including the trailing / [YOCTO #14445] Signed-off-by: Tim Orling <tim.orling@...> --- layerindex/urls.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/laye

Various fixes to address errors and warnings when running update.py The following changes since commit 796d2455bb862ed4c71eadfa9fcf4c002752c2f3: templates/*: staticfiles -> static (2022-01-13 23:36:22

The build patches are now included in the upstream, the local binary checkes can be disabled with --disable-ptool-checks, the boostrap doesn't need to be called if the release .tar.gz is used. Signed-

Calling autoreconf outside git repo causes the version number to be null. This patch makes the version number fixed. Since Yocto now uses OpenSSL 3.0, the file packaging need to be updated. Signed-off

The version number is correctly assigned only when the release .tar.gz is used. Signed-off-by: Petr Gotthard <petr.gotthard@...> --- .../tpm2-abrmd/{tpm2-abrmd_2.4.0.bb => tpm2-abrmd_2.4.1.bb} | 6 ++-

This deletes the patches that were unused for a long time, updates the tpm2-tss package and introduces a fix to the version number problem that got introduced with the 3.2.0 version. Signed-off-by: Pe

Also, the recipe is fixed to correctly package the openssl provider. This new tpm2-openssl: - Fixed segmentation fault when a signature algorithm is beging initialized without a private key. - Fixed R

Calling autoreconf outside git repo causes the version number to be null. This patch makes the version number fixed. Signed-off-by: Petr Gotthard <petr.gotthard@...> --- meta-tpm/recipes-tpm2/tpm2-too

Hello All, This may not be the issue with Yocto itself but rather related to properly booting up Linux on Avenger96(STM32MP1) board. I am currently working on Avenger96 with Yocto(Dunfell). Aim is to

Signed-off-by: Davide Gardenal <davide.gardenal@...> --- recipes-security/fscrypt/fscrypt_1.0.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-security/fscrypt/fscrypt_1.

Add COMPATIBLE_HOST to match what is found in glibc to avoid build error when using musl Signed-off-by: Davide Gardenal <davide.gardenal@...> --- recipes-scanners/clamav/clamav_0.104.0.bb | 2 ++ 1 fil

In the meta-virt builder, don't do a world build but instead build just xen-image-minimal for both qemuarm64 and qemux86-64. This can be expanded over time, but is a sensible starting point and builds

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Luca, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor ARs: - Randy to review AB-INT bugs and adjust/move as necessary - Randy to

Hi all, Currently I cannot recreate my dunfell based image because bitbake fails building go-runtime. I think this commit did build successfully in the past, though. If I recall correctly, the problem

Hello All, I am an experienced Yocto engineer, and I want to contribute to Yocto project (bitbake core, poky layers, etc) but I do not know what to contribute or is there a TODO list that I can help w

I have 3 layers: meta-a: meta-a└── recipes-my └── mypgk ├── mypgk_1.0.bb └── mypkg_rel ├── config.conf └── mypkg.service mypgk_1.0.bb: FILESEXTRAPATHS_prepend_$(MACHINE) := "${THISDIR}/${PN}_rel:"SRC_

Current Dev Position: YP 3.5 M4 Next Deadline: 4th April. 2022 YP 3.5 M4 build Next Team Meetings: Bug Triage meeting Thursday Apr.7th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5