Hi Alex, Could you maybe clarify what you mean with "setting INCOMPATIBLE_LICENSE per image"? Do you mean that you have one specific image that is used when you build an image for release to

I just branched for kirtstone. Should this be backported? -armin

merged thanks, -armin

merged. thanks -armin

Signed-off-by: Anton Antonov <Anton.Antonov@...> --- meta-parsec/README.md | 36 ++- .../parsec-service/files/systemd.patch | 21 +-

In the meta-virt builder, don't do a world build but instead build just xen-image-minimal for both qemuarm64 and qemux86-64. This can be expanded over time, but is a sensible starting point

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Luca, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor ARs: - Randy to review AB-INT bugs and

Hi all, Currently I cannot recreate my dunfell based image because bitbake fails building go-runtime. I think this commit did build successfully in the past, though. If I recall correctly, the

hey Talel, Thanks for reaching out! You are welcome to attend any of the public Yocto developers meetings, if nothing else you will meet and hear directly from the core developers. However it's not

Thanks for the guide. I have one more question regarding the bugs. I noticed that there is a Zoom meeting link, do I need to join it and participate in a discussion about the tasks assignments and try

Hello, I think you can look through Bugzilla for unassigned tasks [1], for example. This one should help on commiting [2]. You should send patches to the relevant mailing list [3]. For the core, it

Hello All, I am an experienced Yocto engineer, and I want to contribute to Yocto project (bitbake core, poky layers, etc) but I do not know what to contribute or is there a TODO list that I can help

Thanks all for your quick response. You have given me something to think of so I will look into it to see if some of my issues are related to the way we have set things up. I will post my findings

Hi I set INCOMPATIBLE_LICENSE_append = " GPLv3 GPLv3+ LGPLv3 LGPLv3+" but then allow compiling several recipes with those licenses as long as they don't end up on images and in the product. For

As you're not naming recipes it is hard to offer concrete advice, but I will note that a large percentage of the bash dependencies in oe-core are specific to the ptest packages. If you don't need

I'd suggest you start by setting INCOMPATIBLE_LICENSE per image, e.g. enable gpl3 ban only in the images that ship to the customers and not across the entire build. Then carefully look at what pulls

Hi, I cannot use GPLv3 packages in our image build. I am no legal expert but from what I can understand most companies will not be able to comply with this license without allowing the customer to

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

On Tue, Apr 5, 2022 at 04:38 PM, Rombola Davide wrote: FILESEXTRAPATHS_prepend_${MACHINE} := "${YOCTOROOT}/meta-a/recipes-my/${PN}/${PN}_rel:" The following line is sayng that you want to select

Current Dev Position: YP 3.5 M4 Next Deadline: 4th April. 2022 YP 3.5 M4 build Next Team Meetings: Bug Triage meeting Thursday Apr.7th 7:30 am PDT