[yocto] NPM support on Dunfell

I'm seeing some gaps and performance issues. Examples: 1. Setting NPM_INSTALL_DEV = "1" I am rewarded with: 169 npm ERR! Could not install from "../../__w/meta-flutter/rpi4-drm-dunfell-latest/raspberr

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

From: 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 readline library support Otherwise, there comes below error during do_configure. $ bitbake bind | configure: error: Package

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

From: Hitendra Prajapati Source: https://github.com/SSSD/sssd MR: 114189 Type: Security Fix Disposition: Backport from https://github.com/SSSD/sssd/commit/7ab83f97e1cbefb78ece17232185bdd2985f0bbe ChangeID: 4588f47f3eeb42a6640e6c1a0d886a9c95f5729c Description: CVE: CVE-2021-3621 sssd: shell comm

[yocto] [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 package sssd, including the .so symlink files. Then it causes QA issues: | ERROR: QA Issue: sssd rdepen

[yocto] 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 packages in a SBOM/manifest randy.macl...

[yocto] Enhancements/Bugs closed WW15!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count ki...@ukr.net 1 tim.orl...@konsulko.com 1 randy.macl...@windriver.com 1 workjagade...@gmail.com 1 Grand Total 4 Thanks, Stephen K. Jolley Yocto Project Program Manager *Cell:

[yocto] 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 release candidates for YP 3.5 needs to be released. Who Count michael.opdenac...@bootlin.com 34

[yocto] 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 the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc

Re: [yocto] Skipping already-stripped check doesn't work

Tested with updated honister branch, same error -- Alessandro Tagliapietra On Mon, Apr 11, 2022 at 2:41 PM Alessandro Tagliapietra < tagliapietra.alessan...@gmail.com> wrote: > I'm using honister (it's from a few months ago, I'm currently > rebuilding using the latest commit) > > On Mon, Apr 1

Re: [yocto] 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) On Mon, Apr 11, 2022 at 2:29 PM Khem Raj wrote: > which release branch are you using? > > On Mon, Apr 11, 2022 at 2:27 PM Alessandro Tagliapietra > wrote: > > > > Removing works, the build succeede

Re: [yocto] Skipping already-stripped check doesn't work

which release branch are you using? On Mon, Apr 11, 2022 at 2:27 PM Alessandro Tagliapietra wrote: > > 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.nod

Re: [yocto] 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 these paths: image/usr/lib/node_modules/node-red-node-serialport/node_modules/@serialport/bindings-cp

Re: [yocto] Skipping already-stripped check doesn't work

On Mon, Apr 11, 2022 at 1:43 PM Alessandro Tagliapietra < tagliapietra.alessan...@gmail.com> wrote: > On Mon, Apr 11, 2022 at 1:36 PM Khem Raj wrote: > >> >> what package folders do you see under packages-split/ folder in your >> build area for this recipe ? >> > > The ones I've added in the INSA

Re: [yocto] Skipping already-stripped check doesn't work

On Mon, Apr 11, 2022 at 1:36 PM Khem Raj wrote: > > what package folders do you see under packages-split/ folder in your > build area for this recipe ? > 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-n

Re: [yocto] Skipping already-stripped check doesn't work

On Mon, Apr 11, 2022 at 1:27 PM Alessandro Tagliapietra wrote: > > 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 packages-split only cont

Re: [yocto] 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 packages-split only contained node-red-node-serialport-* packages. So I've tried to add the skips for

Re: [yocto] 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_ = "arch" eventually is your recipe called node-red-node-serialport ? INSANE_SKIP_${PN} is only accounting for one output package. You

Re: [yocto] Skipping already-stripped check doesn't work

Alessandro Tagliapietra escreveu no dia segunda, 11/04/2022 à(s) 17:13: > 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" >

Re: [yocto] [Question] How to handle GPLv3 packages?

On Mon, Apr 11, 2022 at 1:29 AM Mans Zigher wrote: > > 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 set up > their layers inside the poky di

[yocto] Skipping already-stripped check doesn't work

I've created an npm package recipe for node-red-node-serialport ( https://www.npmjs.com/package/node-red-node-serialport ) using devtool add "npm://registry.npmjs.org;package=node-red-node-serialport;version=1.0.1" which generated this ( https://gist.github.com/alex88/e0e1bca5ac07137229839120f

Re: [yocto] [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 set up their layers inside the poky dir and then they are using COREBASE when one layer depends on t

Re: [yocto] [Question] How to handle GPLv3 packages?

It's a contracting issue. You need to specify in writing that the vendor cannot provide ancient Yocto. Otherwise they won't bother. Alex On Mon, 11 Apr 2022 at 09:13, Måns wrote: > > Yes I know. Not sure why QC is stuck on Thud. Even newer releases from > QC for the target that we are working on

Re: [yocto] [Question] How to handle GPLv3 packages?

Yes I know. Not sure why QC is stuck on Thud. Even newer releases from QC for the target that we are working on is stuck at Thud. Mans Den fre 8 apr. 2022 kl 18:59 skrev Alexander Kanavin : > > Thud has been EOL for a long time. You can see when the support been > added here (end of 2019 it seems