Drop backported patch: 0001-checkpolicy-remove-unused-te_assertions.patch Signed-off-by: Yi Zhao <yi.zhao@...> --- ...ckpolicy-remove-unused-te_assertions.patch | 45 -------------------

* Drop obsolete patch: libsemanage-drop-Wno-unused-but-set-variable.patch * Refresh patch: libsemanage-allow-to-disable-audit-support.patch Signed-off-by: Yi Zhao <yi.zhao@...> ---

Refresh patches: 0001-Do-not-use-PYCEXT-and-rely-on-the-installed-file-nam.patch 0001-Makefile-fix-python-modules-install-path-for-multili.patch Signed-off-by: Yi Zhao

Drop backported and obsolete patches: 0001-Fix-building-against-musl-and-uClibc-libc-libraries.patch libselinux-drop-Wno-unused-but-set-variable.patch Add patch to fix build on musl:

Drop backported patches: 0001-libsepol-fix-CIL_KEY_-build-errors-with-fno-common.patch 0001-libsepol-remove-leftovers-of-cil_mem_error_handler.patch Signed-off-by: Yi Zhao

Signed-off-by: Yi Zhao <yi.zhao@...> --- .../selinux/{selinux_20191204.inc => selinux_20200710.inc} | 2 +- recipes-security/selinux/selinux_common.inc | 3 +-- 2

* Drop backported patches: 0001-Header-definitions-need-to-be-external-when-building.patch 0001-lib-i386_table.h-add-new-syscall.patch Add-substitue-functions-for-strndupa-rawmemchr.patch *

We encountered a runtime error for auditctl on lib32 image for aarch64: root@xilinx-zynqmp:~# auditctl -a always,exit -F arch=b32 -S adjtimex -k TEST-time-change arch elf mapping not found The root

auditd: upgrade 2.8.5 -> 3.0 selinux: upgrade 3.0 -> 3.1 Yi Zhao (17): audit: enable arm/aarch64 processor support by default audit: upgrade 2.8.5 -> 3.0 selinux: upgrade inc files to 3.1

Instead of just providing local.conf info, add layer names and their revisions with bitbake version information into error report makes it easier to understand and reproduce failed build. [YOCTO

It also may be overridden by some conf file. For example, if you are using a i.MX cpus, you may have some conf file on meta-freescale that override this variable with something like:

Thanks for the response. Yes, I tried to set both in local.conif or distro, none of works. There was no PREFERRED_PROVIDER_virtual/kernel, nor PREFERRED_VERSION_linux-yocto setup. Thank you. Kind

Is the PREFERRED_PROVIDER_virtual/kernel set to linux-yocto? You need to set the PREFERRED_VERSION for kernel that you are using ... bitbake -e virtual/kernel output should help see how it's being

Hi, I replaced Linux kernel version from 4.19 by 5.10 bb file, but it still built 4.19 zImage, I add PREFERRED_VERSION_linux-yocto = "5.10%" in local.conf, it still built 4.19 zImage. Where the linux

FWIW this doesn't sound right to me. pyc files (in __pycache__) would cache the code, not data so I don't see how these values would be preserved there. I don't doubt you're seeing some kind of issue

On Sun, 2021-01-03 at 10:44 -0800, Paul D. DeRocco wrote: I've been resurrecting an old Pyro project under Gatesgarth. It's an Intel 32-bit system that needs maximum speed, so I decided to try to

Current Dev Position: YP 3.3 M2 development Next Deadline: 18th January 2021 YP 3.3 M2 build Next Team Meetings: Bug Triage meeting Thursday Jan. 7th at 7:30am PDT

Hi, Where to download Yocto receipt for kernel version 5.10? To update a stable version, should I update Yocto version to 3.3 or 3.1? Thank you. Kind regards, - j

* add support for mingw32 * Engines are installed in a slightly different path, which is urgly, patch it to make the path shorter * remove runtime dependency from perl for mingw nativesdk since

All, YP M+ or high bugs which moved to a new milestone in WW01 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 11449 Allow overriding classes to