You have to find them yourself with gut bisect I would say. Too many things have changed. Alex

<kenth.eriksson@...> wrote: Testing reproducibility properly is a heavy exercise (you need to build everything from scratch, then compare), and so we do it only for glibc. There have been rec

Can you try the tip of master please? Alex

Does this mean that master should be excluded too? Alex

You have to define an additional distribution I'm afraid. It can share almost everything with the existing distro, but set PREFERRED_PROVIDER differently. Alex

Making your own! You can have it added to the layer index for better publicity. Alex

You can start by placing it in a separate layer? Alex

I just wonder if this should really be in core. The standards for core are high: it needs to be both testable and tested, and there's only so many possible options and tweaks where things can regress

This is the correct way, yes. You can put SDKMACHINE into local.conf (default is 'linux sdk'), or you can specify it on command line (in which case it will override the local.conf setting). Alex On Tu

Generally we slim down python installations by not installing all of the standard library, and rather having precise dependencies for specific modules. Can you illustrate the kind of space savings tha

You need to show the whole log. Alex

Then your best option is to drop meta-gplv2 layer from builds altogether. This will update everything to current, compatible versions that are easier to fix if needed. Just to be on the safe side, you

I'm curious as to how though. Are you going to give them a complete set of yocto layers and source code for everything that goes into the image, so that they can replicate the yocto build? If they cho

Combining gpl2 and gpl3 is not an issue here. The issue is that if you ship gpl3 items to users as a part of some product, you have an obligation to allow them to change those items and install the ch

If you're shipping anything that is under gplv3 you also need to give the recipient users a possibility to change the item under gplv3 from the source code you have used to build it and install their

No. You cannot 'just replace' it, as they are under different licenses, and meta-gplv2 specifically collects versions under gpl version 2 only. Are you going to ship what you're working on to other us

I can imagine that meta-gpl2 was in fact added in the first place for exactly that reason. NM is a red hat project, and red hat has no concerns for those pesky embedded linux needs. There's no configu

It may help if you show the complete logs for configure and compile , otherwise there is not enough information in your message to diagnose the issue. Alex

This is probably not available in dunfel, but in master there are bbclasses that handle this: inherit pypi python_setuptools_build_meta So try with master, and then consider your options. Alex

It is not possible to say what went wrong if I cannot see the changes you did, what commands you type, and what is the outcome (vs. what you expect). So you need to publish your code somewhere, and de

#dunfell #patch #yocto #raspberrypi #linux