It’s linker cmdline which is interesting here please post it and that will help to see further

As a first pass, collect all the tmp/buildstats logs using 'cp -a', to enable review and graphing of all builds. The goal is to understand the trends in the /proc/pressure/{cpu|io} data that is now

Hello. Im trying to write a recipe for an autoconf based project. Ive managed to resolve most of the include and linker issues with the exception of the subject error. The files in question exist at

Hi all, I'm trying to debug this issue for quite a while but couldn't get any helpful indication on how to solve it. (In case it matters, the build runs on a docker container with shared volumes for

Hello Quentin, Richard and I eventually did that: disabling the errors on warnings, so that we can make progress on the Sphinx updates and the generation of epub and pdf formats. This won´t prevent

From: Michael Opdenacker <michael.opdenacker@...> This allows to switch to a more recent of Sphinx which will generate warnings with old versions of docs. This way, it's not immediately

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/images/security-build-image.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-core/images/security-build-image.bb

minor recipe cleanup Signed-off-by: Armin Kuster <akuster808@...> --- .../{chipsec_git.bb => chipsec_1.8.5.bb} | 21 +++++++++---------- 1 file changed, 10 insertions(+), 11 deletions(-)

We use the ability to regenerate previous releases to update the switcher lists and potentially other style related changes in future which keeps the docs looking consistent. We may have to disable

Hi Quentin We're trying to build the docs with Sphinx 5.0.0 on a special branch, and we're getting warnings causing the builds to fail:

Current Dev Position: YP 4.1 M2 Next Deadline: 11th July 2022 YP 4.1 M2 Build Next Team Meetings: Bug Triage meeting Thursday June 23rd 7:30 am PDT

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/packagegroup/packagegroup-core-security.bb | 2 ++ recipes-security/Firejail/firejail_0.9.70.bb | 2 ++ 2 files changed,

All, YP M+ or high bugs which moved to a new milestone in WW25 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 5322 Global DNS fallback mechanism not

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 39 bug owners as of the end of WW25 of who have open medium or higher bugs and enhancements against YP 4.1. There are 91 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

Hi , I have been trying to enable Secureboot to my board having Intel-x86 architecture and I am following the steps given in this link https://github.com/jiazhang0/meta-secure-core for Yocto Dunfell

fyi: I started to archive some of the test runs at: https://github.com/akuster/meta-security-testresults Not sure if I am doing this correctly but is at least a snapshot. -armin

Signed-off-by: Armin Kuster <akuster808@...> --- meta-security-compliance/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-security-compliance/README

See changelog for details: https://cisofy.com/changelog/lynis/#308 Signed-off-by: Armin Kuster <akuster808@...> --- .../recipes-auditors/lynis/{lynis_3.0.0.bb => lynis_3.0.8.bb} | 2 +- 1