Cool

Applied to meta-rockchip (with Khem's SoB added) master.

Oops, looks like we both noticed this at about the same time. Since both our patches are identical, I simply added your SoB line. Thanks!

Applied to meta-rockchip master. Thanks!

Maybe? https://github.com/python/docsbuild-scripts/ Found on https://pythondev.readthedocs.io/infra.html

docs.pythong.org is where we stole the idea of the switcher ;-) Would anyone be able to figure out if their 'publishing' script is available anywhere? if we could mimic that somehow that might be

Quentin, Nico, Thanks for your reviews. Good to know that the "transition" branch is still in use in spite of what I wrongly believed. It indeed, it's a good idea to see what other projects are

meta-arm has dropped exporting virtual/trusted-firmware-a and expects direct use of trusted-firmware-a on depends sections Signed-off-by: Khem Raj <raj.khem@...> ---

Note that using grub-efi on aarch64 is expected and normal, building "grub" is not. I think the core-image-minimal-initramfs recipes and/or initramfs-module-install recipes need a bit of

The latest trusted-firmware-a recipe in meta-arm no longer considers trusted-firmware-a to have potentially multiple providers. Signed-off-by: Trevor Woerner <twoerner@...> ---

This has been included upstream see [1] [1] https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/f943b7c8e292e3aad2fcbdd0a37505f62b3b4c87%5E%21/#F0 Signed-off-by: Khem Raj

Hi Quentin, Thanks for the review and for your suggestions. I tried, but I stumble on the need to copy the latest switchers.js from yocto-docs to the Bitbake branches too. And since the Bitbake

I am also interested in helping move this forward, please count me in. Scott

Dear all, My goal is to have a squashfs rootfstype and ext4 data partition that get combined in an overlayfs and switched to the root during boot. I managed to get the overlayfs and switching of

Hi, You could also consider using the `BBFILES_DYNAMIC`[1] variable, this way your bbappend would only apply when there is `meta-raspberrypi` in the build configuration. Your bbappend could be placed

You can either use BBMASK in your local.conf to remove the bbappend from the parsing tree or set BB_DANGLINGAPPENDS_WARNONLY in your specific build. both can be added to your specific kas yaml

Dear all, My situation is as follows: Using Kas container to build and enable easy CI, I have 2 .yaml files creating my 2 builds for 2 different machines: RaspberryPi and Qemu. Qemu yaml file

Drop backport CVE patches. Signed-off-by: Yi Zhao <yi.zhao@...> --- ...{checkpolicy_3.2.bb => checkpolicy_3.3.bb} | 0 ...python_3.2.bb => libselinux-python_3.3.bb} | 0

There are too many recipes in recipes-security/selinux. Keep the selinux userspace recipes and move selinux scripts to selinux-scripts directory to make the directory hierarchy

Add RDEPENDS on audit-python for selinux-python-semanage. Fixes: $ semanage fcontext -a -t user_home_t "/web(/.*)?" Traceback (most recent call last): File "/usr/sbin/semanage", line 975, in