I would like to work our how we can improve this situation, I'm just struggling to see what we should do :/ Cheers, Richard

I think the Unicode should be clear, as the tool (in)directly uses downloads from unicode, but kindly ignores the licensing part of that operation. Looking into the history of that lib I found

<quentin.schulz@...> wrote: I looked at https://github.com/kjd/idna/blob/master/LICENSE.md https://pypi.org/project/idna/ and they seem to indicate that it is BSD-3-Clause so where

Hi Alex, It's not a case of simply deleting the so files we don't need since the mesa build system stuffs everything into a small number of files and then hard links them together. For example, the

After some discussion with Richard on #yocto irc we've decided to drop the patch status updates from this series. The following changes since commit 44b1970c40e9d73f6e63fb10cdc55837a26f5921:

Unfortunatley this breaks building python3-native. Although it compiles, during the build the python build scripts tries to import the created modules, and if this fails (which it does) it renames the

Cc'ing licensing@... to hopefully get knowledgeable people on the topic? Thanks, Quentin

Thanks Bruce. Kevin

ok. Let's solve this with an explicit KBRANCH with your pinned SRCREVs for now, and I'll update -dev to use versioned branches for the current 5.16 cycle and all new versions that follow. Bruce --

From: Alexander Kanavin <alex.kanavin@...> This adds a smoke check for whether the Go toolchain actually produces working executables across a range of architectures. (From OE-Core rev:

Another crazy thought is our sstate really is already path independent, regardless of the binary content. You could therefore make the hash function replace the path with a fixed string. The downside

Right, I'll give it a try. I know the build path will change if I upgrade to a new version of gcc, but then the output is most definitely gonna change as well. I was thinking if it was possible to

I'm wondering if: -Wl,-rpath,/not/exist/our-native-libdir-marker -Wl,-rpath,/not/exist/our-native-base-libdir-marker would work. We originally started here with gcc-cross so lets consider that and

Hmm not sure I follow. This patch adds a new dummy rpath entry, "/rpath-padding-xxx...", then we remove it in chrpath. I don't know what other value we would like to put there. If I understand you

From: Ranjitsinh Rathod <ranjitsinh.rathod@...> It seems like CVE-2021-33928, CVE-2021-33929, CVE-2021-33930 and CVE-2021-33938 are pointing to same patch as CVE-2021-3200 So add CVE tag inside

From: Ranjitsinh Rathod <ranjitsinh.rathod@...> Add patch to fix CVE-2021-39537 Link:

From: Ranjitsinh Rathod <ranjitsinh.rathod@...> Add patch to fix CVE-2021-43618 Link: https://gmplib.org/repo/gmp-6.2/rev/561a9c25298e Signed-off-by: Ranjitsinh Rathod

I've several tries, and append -D works well This is my original trying, if above failed in some cases, we have to give up to support determinism for @ //Hongxu

I am a little surprised this works, since "-D" would be placed after any archive/member parameters. But if does, ok. Otherwise maybe we should just give up if there is a '@' and fallback to not

If ar input params starts with @, it means to read options from file $ ar -h ... @<file> - read options from <file> ... It failed to call ar wrapper to read options from file: $