[yocto] [meta-security][PATCH 2/2] update chipsec to 1.8.8

Signed-off-by: Armin Kuster --- recipes-security/chipsec/{chipsec_1.8.7.bb => chipsec_1.8.8.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename recipes-security/chipsec/{chipsec_1.8.7.bb => chipsec_1.8.8.bb} (94%) diff --git a/recipes-security/chipsec/chipsec_1.8.7.bb b/recipes-se

[yocto] [meta-security][PATCH 1/2] update sssd to 2.7.4

Signed-off-by: Armin Kuster --- .../recipes-security/sssd/{sssd_2.7.3.bb => sssd_2.7.4.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename dynamic-layers/networking-layer/recipes-security/sssd/{sssd_2.7.3.bb => sssd_2.7.4.bb} (98%) diff --git a/dynamic-layers/networking-laye

Re: [yocto] Bitbake + Patches

Sorry for not responding earlier. I do not read this list regularly. The values I supplied for the suggested bbappend all come from the version of the apache2 recipe that is on master of the openembedded repository. If you change the version from 2.4.54 to 2.4.52, then yes, you will have to chan

Re: [yocto] Update upstream kirkstone branches

Hi Paulo, On 9/6/22 16:20, pa...@eero.com wrote: Hello all! I've been just recently working with Yocto at my new position and just ran into an issue that was already solved on Yocto's main branches for both openembedded and poky layers. There's a problem with npm on upstream kirkstone, where

[yocto] CVE patch application - best way to do it

Hi team, With respect to the feature "CVE_CHECK" provided by Yocto, what is the best approach to deploy the patches reported by the CVE? It's definitely not a good approach to patch using a blind approach but once we've defined the required CVE, does Yocto can do the updates based on a definit

[yocto] Yocto Project Status 6 September 2022 (WW36)

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

[yocto] Update upstream kirkstone branches

Hello all! I've been just recently working with Yocto at my new position and just ran into an issue that was already solved on Yocto's main branches for both openembedded and poky layers. There's a problem with npm on upstream kirkstone, where the fetching of dependencies fails due to stale or

[yocto] [meta-security][V2][PATCH] cryptmount: fix systemd service install

Default is to install the service in /usr/lib Signed-off-by: Armin Kuster -- [V2] Fix typo in subject --- .../sssd/{sssd_2.7.3.bb => sssd_2.7.4.bb} | 2 +- .../{chipsec_1.8.7.bb => chipsec_1.8.8.bb}| 2 +- .../cryptmount/cryptmount_5.3.3.bb| 10 + .../krill/files/p

[yocto] [meta-zephyr][PATCH 5/5] zephyr-kernel: Add 'zephyr' toolchain variant

From: Peter Hoyes Add an option to build applications using the Zephyr SDK by specifying ZEPHYR_TOOLCHAIN_VARIANT="zephyr". This mode works with the zephyr or poky distros (TCMODE is ignored), allowing Zephyr applications to be built alongside a Linux stack. Provide a toolchain-specific inc file

[yocto] [meta-zephyr][PATCH 4/5] zephyr-sdk: Add recipe to download and build the Zephyr SDK

From: Peter Hoyes The Zephyr SDK (https://github.com/zephyrproject-rtos/sdk-ng) provides pre-built toolchains for all of Zephyr's supported architectures. Add a recipe to download SDK v0.14.2, in preparation for adding an option to build Zephyr applications using this toolchain instead of the Yo

[yocto] [meta-zephyr][PATCH 3/5] zephyr-kernel: Factor out Yocto toolchain specific variables

From: Peter Hoyes Create ZEPHYR_TOOLCHAIN_VARIANT variable with an unchanged default value of 'yocto'. To support providing different configuration for different toolchain variants, require a toolchain-specific inc file. Create zephyr-toolchain-yocto.inc, and factor out all variables that are s

[yocto] [meta-zephyr][PATCH 2/5] CI: Use the matrix to ovleray additional Kas files

From: Peter Hoyes Adopt the jobs-to-kas helper script from meta-arm, which uses Gitlab's parellel matrix to overlay additional Kas files on top of the base Kas file (based on $CI_JOB_NAME). This allows multiple combinations of Kas file overlays to be easily tested with minimal boilerplate. Sign

[yocto] [meta-zephyr][PATCH 1/5] Cleanup README.txt files

From: Peter Hoyes The README.txt files at the root and in meta-zephyr-core are identical, so replace the copy inside meta-zephyr-core with "See ../README.txt" to remove the need to keep two files in sync. Add a similar README.txt to meta-zephyr-bsp. Signed-off-by: Peter Hoyes --- meta-zephyr-

[yocto] Kirkstone QA already-stripped problem to install binary

We have an issue with a custom recipe which includes a pre-build binary. Before migrating to Kirkstone 4.0.1 we were able to build the recipe using >INSANE_SKIP:${PN} += "already-stripped"<, but this now failed with: ERROR: intel-docker-compose-2.2.2-r0 do_package: QA Issue: File '/usr/bin/docker-