openembedded-devel@lists.openembedded.org

Home Messages Hashtags Subgroups

Messages

Between

and

Re: [meta-oe][PATCH] layer.conf: Post release codename changes

This is kind of promise than reality at this point. True, although I wonder if there will be a case where we wont be compatible with langdale in master Logically yes.

By Khem Raj · #96816 ·

Re: [meta-oe][PATCH] layer.conf: Post release codename changes

Isn't it a bit premature to claim langdale compatibility when we don't know what changes langdale will need? I think it makes more sense to add this at the end of cycle, not at the beginning. Regards,

By Martin Jansa · #96815 ·

Honister customer defconfig replacement doesn't work

Hello, My apology, I am not sure which group is working on defconfig syntax for version 3.4 Honister branch. I posted the question to Yocto list without response, let me rephrase it again: According

By JH <jupiter.hce@...> · #96814 ·

[meta-oe][PATCH] layer.conf: Post release codename changes

Post release add langdale to match core Signed-off-by: Armin Kuster <akuster808@...> --- meta-filesystems/conf/layer.conf | 2 +- meta-gnome/conf/layer.conf | 2 +-

By Armin Kuster · #96813 ·

[meta-oe][PATCH] boinc-client: Make script install not depend on host install paths

The install target is checking for install paths on build host assuming thats where it will run too, which breaks cross builds. Add a patch to aide the install from recipe. Signed-off-by: Khem Raj

By Khem Raj · #96812 ·

[meta-python][PATCH] python3-pyfanotify: new package

This adds a recipe for pyfanotify - a python wrapper around linux' fanotify interface. Signed-off-by: Bartosz Golaszewski <brgl@...> --- .../packagegroups/packagegroup-meta-python.bb | 1 +

By Bartosz Golaszewski · #96811 ·

Re: CVE-check failing on world with meta-openembedded: diff.gz file

Adding Ross, Richard and Steve. I'm wondering if it makes sense to consider .diff.gz (or .patch.gz) files as patches for cve-check. They basically come directly from 3rd parties and it is quite

By Marta Rybczynska · #96810 ·

Re: [meta-oe][PATCH v2] nodejs: add option to use openssl legacy providers again

We have such bbclass already: https://github.com/webosose/meta-webosose/blob/master/meta-webos/classes/webos_npm_env.bbclass but I didn't want to enable legacy providers globally, so I was adding it

By Martin Jansa · #96809 ·

Re: [meta-oe][PATCH v2] nodejs: add option to use openssl legacy providers again

Maybe you can try to add it into global npm class with some enabling variable. Cheers, Andrej On Tue, 2022-04-26 at 14:59 +0200, Martin Jansa wrote:

By Andrej Valek · #96808 ·

[meta-oe][PATCH] lockdev: Drop cumulative debian patch

This patch is essentially defines MAXPATHLEN which no longer is problem with latest glibc or musl define MAJOR/MINOR for non-glibc case Signed-off-by: Khem Raj <raj.khem@...> Cc: Marta

By Khem Raj · #96807 ·

Re: CVE-check failing on world with meta-openembedded: diff.gz file

Hi Marta I think this option looks best or perhaps we should drop applying debian diff entirely since debian seems to have dropped this package I think regardless of what we do with this package it

By Khem Raj · #96806 ·

Re: [meta-oe][PATCH 1/2] atkmm: Allow build with wayland

On Tue, Apr 26, 2022 at 5:12 PM Khem Raj <raj.khem@...> wrote: Thanks. Just a minor nit: Could you change commit message to 'atkmm: Allow build with wayland only' because it builds fine with

By Andreas Müller · #96805 ·

[meta-oe][PATCH 2/2] pangomm: Allow building with wayland

Signed-off-by: Khem Raj <raj.khem@...> Cc: Andreas Müller <schnitzeltony@...> --- meta-oe/recipes-graphics/pango/pangomm_2.46.2.bb | 3 ++- 1 file changed, 2 insertions(+), 1

By Khem Raj · #96804 ·

[meta-oe][PATCH 1/2] atkmm: Allow build with wayland

Signed-off-by: Khem Raj <raj.khem@...> Cc: Andreas Müller <schnitzeltony@...> --- meta-oe/recipes-gnome/atk/atkmm-2.36_2.36.1.bb | 2 +- meta-oe/recipes-gnome/atk/atkmm_2.28.2.bb |

By Khem Raj · #96803 ·

Re: [meta-networking][PATCH] frr: add PACKAGECONFIG for fpm

OK. I will look into it. Thanks. //Yi

By Yi Zhao · #96802 ·

Re: [meta-oe][PATCH v2] nodejs: add option to use openssl legacy providers again

export OPENSSL_MODULES="${STAGING_LIBDIR_NATIVE}/ossl-modules" export NODE_OPTIONS="--openssl-legacy-provider" is what I'm doing in recipes which need it now. > you should have a legacy libraries in

By Martin Jansa · #96801 ·

Re: [meta-oe][PATCH v2] nodejs: add option to use openssl legacy providers again

Hi, of course, that i working. But if you're going to use --openssl-legacy-provider, you should have a legacy libraries in library loading path already. Other option is manually set variables in

By Andrej Valek · #96800 ·

Re: [meta-oe][PATCH v2] nodejs: add option to use openssl legacy providers again

Hi, does this work correctly for you with nodejs-native? Here it fails to load legacy module: recipe-sysroot-native/usr/bin/node -p 'crypto.createHash("md4")' --openssl-legacy-provider Unable to load

By Martin Jansa · #96799 ·

Re: CVE-check failing on world with meta-openembedded: diff.gz file

Khem, Any feedback about this? From the history it looks like it was you who changed the recipe to use the .diff.gz file. Thanks in advance, Marta

By Marta Rybczynska · #96798 ·

[meta-multimedia][PATCH] pipewire: Upgrade to version 0.3.50

This is a bugfix release. Notably, this makes pw-dot work again - it required workarounds via pw-dump to output a non-empty dot graph in 0.3.4= 9. Full

By Carlos Rafael Giani · #96797 ·

6061 - 6080 of 102874

Home Hashtags Subgroups Terms