Add UPSTEAM_CHECK Signed-off-by: Armin Kuster <akuster808@...> --- recipes-scanners/clamav/clamav_0.104.0.bb | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

There is the oe-stylize.py script that attempts to format recipes according to the style guide: https://git.openembedded.org/meta-openembedded/tree/contrib/oe-stylize.py Last time I played with it, I

Includes gcc11 fix. Added p11-kit Minor cleanup Signed-off-by: Armin Kuster <akuster808@...> --- .../recipes-tpm2/tpm2-pkcs11/files/677.patch | 295 ++++++++++++++++++ ...2-pkcs11_1.5.0.bb =>

Last update was 2018. Does not build with gcc11. There are other actively maintained IDS options. Signed-off-by: Armin Kuster <akuster808@...> ---

Anyone?

When you install files during do_install, you need to be clear about who you want to own the end result. If you do something like "touch ${D}/x", the it will be owned by the default user which in a

From: Andrei Gherzan <andrei.gherzan@...> The runqemu script depends on having the native sysroot populated for the qemu recipes. Add the required dependency to the mix. Signed-off-by: Andrei

Hi! I try to create a libcryptopp package for my yocto build with the appended bb-recipe. That worked without problems on my old build server with Yocto 3.0. Now I have moved to a new build server

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.4.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2.

Ok. Thanks. I can confirm that the change of the bitbake users UID to 1111 did not solve the issue. I will open a new thread because I don't see why this fails. I use oe_runmake in my do_install

A build flagged for QA (yocto-3.2.4.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.2.4.rc1 Build hash information: bitbake:

Thanks… I forgot that… linked. I appreciate the help. Steve

I'm pleased to be able to announce that the project is planning to have the April 2022 release next year be our next LTS release. This fits in with our original announced plan of 2 year cycles

The -j option has the side effect that the output is cached. For a long running single threaded target, the live output is more useful so switch to it. Signed-off-by: Richard Purdie

No, you should chown the files to be owned by the expected user which exists in the image (probably root like in my commit). Changing the UID of the user on host is very bad work around (as it will

This should be fixed in master, the issue was triggered by a checkout  owned by root/root: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=eff192abe2ee43ebf981bafbb7fca8602ebdcf0c Steve/Anuj:

Hi Martin! I have here a similar problem with one of my own packages. It happens that my bitbake user uses UID 1001. Do you have more information why this is a problem? Should it be enough to change

Adding BB_ORIGENV to do_compile[vardepsexclude] solved the issue. Thanks for your help!

Hi Richard, Unfortunately, that doesn't make the error messages go away. I agree that it's not great that go-mod fetches during do_compile but that's the way it currently is. For completeness sake,

right, that's what if we want to do this then it has to be persisted with otherwise it will end up being one time exercise with all these losses you described.