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,

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 o

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 l

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

Just like the .patch file in master branch, does hardknott have stricter rules than master branch?

* the branch was renamed in upstream * it's already resolved in meta-oe/kirkstone since this commit: commit cef2d1429bedbc256c5fac7a1a336842865dc2d3 Author: Robert Joslyn <robert.joslyn@...

From: Khem Raj <raj.khem@...> * based on commit from honister, but without the upgrade: commit 8691de2580dd872e3d001d67c8455108b3bd627c Author: Khem Raj <raj.khem@...> Date: Sat May 8 14:3

* fixes: ERROR: Nothing RPROVIDES 'x265' (but meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb RDEPENDS on or otherwise requires it) x265 was skipped:

* the branch was renamed in upstream * it's already resolved in meta-oe/kirkstone since this commit: commit cef2d1429bedbc256c5fac7a1a336842865dc2d3 Author: Robert Joslyn <robert.joslyn@...

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index c91335d..38ef579 1006

* openembedded-core/scripts/contrib/convert-spdx-licenses.py . ... All files processed with version 0.01 Signed-off-by: Martin Jansa <Martin.Jansa@...> --- recipes-connectivity/gateone/gateone_g

* openembedded-core/scripts/contrib/convert-variable-renames.py meta-* ... All files processed with version 0.1 Signed-off-by: Martin Jansa <Martin.Jansa@...> --- conf/distro/include/python2-tar

* fixes: meta-oe/meta-networking/recipes-support/strongswan/strongswan_5.9.4.bb:125: DeprecationWarning: invalid escape sequence \. meta-oe/meta-networking/recipes-support/strongswan/strongswan_5.9.4.

This should be sent to oe-core ML.

* distutils removal in Python 3.12 doesn't affect already EOL Python2 recipes Signed-off-by: Martin Jansa <Martin.Jansa@...> --- classes/distutils-base.bbclass | 32 +++++++++++++++++++++++++++++

agreed, with dash nodejs do_install fails with dash: tmp-glibc/work/x86_64-linux/nodejs-native/16.11.1-r0/temp/run.do_install.2837733:169: [[: not found but unfortunately it doesn't cause do_install t

This version fails to build here with: | ../git/configure: line 3778: syntax error near unexpected token `noext' | ../git/configure: line 3778: `AX_CXX_COMPILE_STDCXX_17(noext)' switching back to olde

This version fails to build here with:| ../git/configure: line 3778: syntax error near unexpected token `noext' | ../git/configure: line 3778: `AX_CXX_COMPILE_STDCXX_17(noext)' switching back to older

> The build system might have put something into DEPENDS already There is only copyright notice before this chunk, so this doesn't make much sense to me (and no other recipe does this).

most likely to enable the PACKAGECONFIG to build them recipes-qt/qt5/qt5.inc:PACKAGECONFIG[examples] = "" recipes-qt/qt5/qt5.inc:EXTRA_QMAKEVARS_PRE += "${@bb.utils.contains('PACKAGECONFIG', 'examples