yocto@lists.yoctoproject.org

[meta-gplv2][PATCH] readline: add config file for pkgconfig

From: Mingli Yu <mingli.yu@...> After bind upgrade to 9.18.x, the below change introduced [1], all supported libraries have accompanying .pc files now. ba2376b9e0 Update and cleanup the

By Yu, Mingli · #56736 ·

[meta-security][dunfell][PATCH 2/2] sssd: CVE-2021-3621: shell command injection in sssctl

From: Hitendra Prajapati <hprajapati@...> Source: https://github.com/SSSD/sssd MR: 114189 Type: Security Fix Disposition: Backport from

By Jeremy Puhlman · #56735 ·

[meta-security][dunfell][PATCH 1/2] sssd: re-package to fix QA issues

Source: meta-security:honister MR: 113808 Type: Defect Fix Disposition: Merged from honister ChangeID: be0e4f3c73eeb04d1c79d99d3377c89659abe420 Description: It packages all file in ${libdir} to

By Jeremy Puhlman · #56734 ·

M+ & H bugs with Milestone Movements WW15

All, YP M+ or high bugs which moved to a new milestone in WW15 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 14495 Implement CVE checking on all

By Stephen Jolley · #56733 ·

Enhancements/Bugs closed WW15!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count kit-d@... 1 tim.orling@... 1 randy.macleod@... 1 workjagadeesh@... 1 Grand Total 4 Thanks,

By Stephen Jolley · #56732 ·

Current high bug count owners for Yocto Project 3.5

All, Below is the list as of top 38 bug owners as of the end of WW15 of who have open medium or higher bugs and enhancements against YP 3.5. There are 13 possible work days left until the final

By Stephen Jolley · #56731 ·

Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

By Stephen Jolley · #56730 ·

Re: Skipping already-stripped check doesn't work

Tested with updated honister branch, same error -- Alessandro Tagliapietra

By Alessandro Tagliapietra · #56729 ·

Re: Skipping already-stripped check doesn't work

I'm using honister (it's from a few months ago, I'm currently rebuilding using the latest commit)

By Alessandro Tagliapietra · #56728 ·

Re: Skipping already-stripped check doesn't work

which release branch are you using? <tagliapietra.alessandro@...> wrote:

By Khem Raj · #56727 ·

Re: Skipping already-stripped check doesn't work

Removing works, the build succeeded, however I can't test if it's actually needed by the package, I'll try that tomorrow. Regarding file paths for example file linux-arm/node.napi.armv7.node is in

By Alessandro Tagliapietra · #56726 ·

Re: Skipping already-stripped check doesn't work

Ok then next thing you want to check is where the reported stripped file is located and even if it does not work then perhaps look into removing these files if they are not needed

By Khem Raj · #56725 ·

Re: Skipping already-stripped check doesn't work

The ones I've added in the INSANE_SKIP ls -lah /home/alex/Projects/yocto/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/node-red-node-serialport/1.0.1-r0/packages-split total 32K drwxr-xr-x

By Alessandro Tagliapietra · #56724 ·

Re: Skipping already-stripped check doesn't work

<tagliapietra.alessandro@...> wrote: what package folders do you see under packages-split/ folder in your build area for this recipe ?

By Khem Raj · #56723 ·

Re: Skipping already-stripped check doesn't work

Thank you for helping! The package is node-red-node-serialport, it doesn't seem to create child packages for the dependencies, the nodejs deps only reside in the package node-modules folder. The

By Alessandro Tagliapietra · #56722 ·

Re: Skipping already-stripped check doesn't work

The prebuilds are for other architectures. so perhaps you can rm them in a do_install_append() or if they are really needed you perhaps would also need INSANE_SKIP_<name of package> = "arch"

By Khem Raj · #56721 ·

Re: Skipping already-stripped check doesn't work

Alessandro Tagliapietra <tagliapietra.alessandro@...> escreveu no dia segunda, 11/04/2022 à(s) 17:13: Hi Alessandro, This is because the package that you are building is already compiled and there

By Jose Quaresma · #56720 ·

Re: [Question] How to handle GPLv3 packages?

This will be valiant effort but my advice is don't go alone if you want to undertake this SOC sdks have lot of nitty gritty issues that will pop up along the way and unless you have someone from SOC

By Khem Raj · #56719 ·

Skipping already-stripped check doesn't work

I've created an npm package recipe for node-red-node-serialport using devtool add "npm://registry.npmjs.org;package=node-red-node-serialport;version=1.0.1" which generated this recipe. The problem is

By Alessandro Tagliapietra · #56718 ·

Re: [Question] How to handle GPLv3 packages?

This is my first time working with them so I am learning a lot but never encountered anything like it. Trying to look into what it would require to move to a newer version it appears as if they have

By Mans Zigher <mans.zigher@...> · #56717 ·

Messages