right, so usually it means maintainers keep master moving forward and perhaps test with latest release or master or perhaps all releases after the thud branch, you have to ask this question to the

Hi Anders, I haven't played with that for a while but I'm pretty sure the answer is yes, it's intentional. You can read about reproducible builds here:

It's a simple operation. They check for the existence of /etc/apparmor.d/cache. If it doesn't exist, then they create it as a directory. I'm not sure why it can't be moved elsewhere, as we're not the

The right way would be to fix the recipe I think? What is doing that has to happen only on target and can't be done during do_rootfs? Alex

The recipe is apparmor, layer is meta-security. We're currently using the 2.x recipe, however the 3.x recipe appears to have the same function.

What recipe is it and what layer is it in? Alex

Hey folks, We're doing builds using Yocto 3.1 and are attempting to revise a recipe from another layer we don't control. The recipe we want to make alterations to is from an open source project, so

Hi All, I'm in serious task here and I need to cross compile a Cmake project. I need to send an SDK to a client with steps to cross compile the project. This project is compiling successfully via a

merged thanks

merged thanks

colleague wants to add some perl recipes to a zeus-based image, and found the meta-cpan layer, which contains a number of desired recipes, but the structure of that layer seems a bit sparse. first,

Hi, I'm trying to install different fstab files based on the image being built. As far as I can tell this should be possible by using BBCLASSEXTEND. The error I get is: Error: Transaction check

Hello, We are pleased to announce the Yocto Project 3.2 (gatesgarth-24.0.0) Release is now available for

No. meta-oe is lower in the stack so I should drop the one in meta-security and update the one in meta-oe. I didn't notice the recipe already existed. its all about timing and effort at this point. we

Hi, Was going over recipes that were duplicated over layers, and this one is a newer version of a similar recipe that is already in meta-oe (which is a dependency of this layer). Should we drop the

refresh a few patches too Signed-off-by: Armin Kuster <akuster808@...> --- ...-avoid-searching-host-for-postgresql.patch | 15 ++--- .../samhain-configure-add-option-for-ps.patch | 66

Thanks, that was my issue... did not read it carefully enough. Keep in mind zeus is totally different from rock... running down multiple issues, sorry, I appreciate the your time/help, thanks

> I was use using https... that is a typo, sorry... Then fix your typo and it will work, but I think you didn't read what I wrote carefully enough, see the url in the log you pasted: zeus: URL

Current Dev Position: YP 3.3 M1 development Next Deadline: 7th December 2020 YP 3.3 M1 build Next Team Meetings: Bug Triage meeting Thursday Nov. 5th at 7:30am PDT

When using ./meta/recipes-core/ovmf/ovmf_git.bb as provided by Yocto I get the following error... WARNING: ovmf-native-edk2-stable201905-r0 do_fetch: Failed to fetch URL