Signed-off-by: Martin Jansa <Martin.Jansa@...> --- ...b-fix-compatibility-with-python-3.11.patch | 76 +++++++++++++++++++ .../recipes-benchmark/glmark2/glmark2_git.bb | 3 +- 2 files changed, 78

* hardknott and newer branches don't need this as upb repo was removed in: commit 15cff67fd6cdb34e3621368fe9ce94a98356f27a Author: Anatol Belski <anbelski@...> Date: Fri Feb 19 12:39:5

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta-oe/recipes-dbs/leveldb/leveldb_1.22.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-dbs/leveldb/level

From: Mingli Yu <mingli.yu@...> Fix the below do_fetch warning: WARNING: bridge-utils-1.7-r0 do_fetch: Failed to fetch URL git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/bridge-uti

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta-oe/recipes-graphics/tesseract/tesseract-lang_4.0.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-gr

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta-oe/recipes-graphics/tesseract/tesseract-lang_4.1.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-gr

On Wed, Mar 30, 2022 at 11:29 PM Trevor Woerner <twoerner@...> wrote: On Wed 2022-03-30 @ 04:08:31 PM, Richard Purdie wrote: > On Wed, 2022-03-30 at 09:40 -0400, Trevor Woerner wrote: > > Hi Mat

buildroot removed it in 2019 and recommends to use busybox version instead:https://github.com/buildroot/buildroot/commit/2b2579afebfc7a9b8a458af1f2d206101fbfa19c "Use the the Busybox devmem utility, i

The history of this is deep :) https://git.openembedded.org/openembedded/log/packages/devmem2?h=master https://git.openembedded.org/openembedded/log/recipes/devmem2?h=master https://git.openembedded.o

Anyone willing to create a repo for this on github instead of patching this in metadata? This is another reproducer for do_patch issue described here https://lists.yoctoproject.org/g/yocto/message/566

Replace this with RDEPENDS:${PN}-dev = ""

* based on this bbappend from 2012: https://github.com/openwebos/meta-webos/commit/f4745112438a5ba1913708b6b6ac30234ec8076e time to finally get rid of it Signed-off-by: Martin Jansa <Martin.Jansa@gmai

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta-oe/recipes-extended/ostree/ostree_2020.3.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-extended/ost

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta-oe/recipes-extended/ostree/ostree_2022.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-extended/ost

* backport the actual code change from https://github.com/pyca/cryptography/pull/5747 without the docs and CI changes (which aren't applicable on old 2.8 version) and backport 2 older changes to make

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?