[oe] [meta-networking][PATCHv2] blueman: skip buildpath error

Blueman has compiled the buildpath into _blueman.so. The underlying issue is related to the cython compiler, so theres nothing that can be done from the blueman side. [https://github.com/cython/cython/issues/5949] Disable the buildpath error to keep blueman usable until the problem is fixed. Sign

Re: [oe] [meta-networking][PATCH] blueman: skip buildpath error

Got it. Thanks for your further explanation. Regards, Qi From: Markus Volk Sent: Thursday, August 8, 2024 2:04 AM To: Chen, Qi Cc: Markus Volk ; openembedded-devel@lists.openembedded.org Subject: Re: [oe] [meta-networking][PATCH] blueman: skip buildpath error I'm not absolutely sure either. Bu

[oe] [meta-oe][scarthgap][PATCH 2/2] python3-grpcio: backport abseil-cpp RISC-V fix

Backport upstream abseil-cpp fix[1] for SIGILL crash on RISC-V with 6.6 and newer kernels. The patch has been tweaked to apply on top of the existing patch stack to the vendored copy of abseil-cpp. [1]: https://github.com/abseil/abseil-cpp/commit/7335a36d (cherry-picked from 080287ebe1f695808887

[oe] [meta-oe][scarthgap][PATCH 0/2] python3-grpcio patch backports

Backport a couple of fixes from master, Martin's allows building python-grpcio-native on hosts with gcc 14 (something I need for building AGL on e.g. Fedora 40), and the second is a fix for a runtime crash on RISC-V that I noticed has not yet backported. Martin Jansa (1): python3-grpcio: Fix bui

[oe] [meta-oe][scarthgap][PATCH 1/2] python3-grpcio: Fix build with gcc-14

* crypto: use _Generic only if !defined(__cplusplus) * fixes build with gcc-14 which has __builtin_addc and __builtin_subc with gcc-13 it was already using the #else branch because of missing builtins * fixes https://github.com/grpc/grpc/issues/35945 http://errors.yoctoproject.org/Errors/De

Re: [oe] [meta-networking][PATCH] blueman: skip buildpath error

I'm not absolutely sure either. But what happens is what is described here: cython creates a variable in _blueman.c that stores the path where the blueman module was built: static const char __pyx_k_home_flk_poky_build_hypr_tmp_wo[] = "/home/flk/p

Re: [oe] [meta-python][PATCHv2] python3-qrcode: switch to PEP-517 build backend

Thanks for all the patches for fixing this PEP-517 build issues. It would be good if you sent them as a single series instead of individual patches, this would help us maintainers who use tools to get patches from mailing list using b4 etc. On Wed, Aug 7, 2024 at 6:14 AM Alper Ak via lists.openemb

[oe] [meta-multimedia][PATCH v2] libcamera: Add support for pycamera

Supply a libcamera-pycamera package to allow installing the libcamera python bindings. Signed-off-by: Kieran Bingham --- v2: - Fix 'meta-multimedia' in subject - Deliver to openembedded-devel instead of openembedded-core .../recipes-multimedia/libcamera/libcamera_0.3.0.bb | 4 +++-

[oe] [meta-python][PATCH] python3-qrcode:

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-qrcode-7.4.2-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by: alp

[oe] [meta-python][PATCH] python3-evdev: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-evdev-1.7.1-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by: alpe

[oe] [meta-python][PATCH] python3-click-repl: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-click-repl-0.3.0-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by:

[oe] [meta-python][PATCH] python3-pykickstart: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-pykickstart-3.48-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by:

[oe] [meta-python][PATCH] python3-screeninfo: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the poetry.core.masonry.api PEP-517 backend. Fix: WARNING: python3-screeninfo-0.8.1-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with poetry.core.masonry.api, use the correct class [pep517-backend] Signed-of

[oe] [meta-python][PATCH] python3-term: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-term-2.5-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by: alperak

[oe] [meta-python][PATCH] python3-pyaudio: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-pyaudio-0.2.14-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by: a

[oe] [meta-python][PATCH] python3-can: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-can-4.2.2-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by: alpera

[oe] [meta-python][PATCH] python3-pymongo: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-pymongo-4.7.3-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by: al

[oe] [meta-python][PATCH] python3-brotli: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-brotli-1.1.0-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by: alp

[oe] [meta-python][PATCH] python3-dbus-fast: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the poetry.core.masonry.api PEP-517 backend. Fix: WARNING: python3-dbus-fast-2.22.1-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with poetry.core.masonry.api, use the correct class [pep517-backend] Signed-off

[oe] [meta-python][PATCH] python3-bitstruct: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fix: WARNING: python3-bitstruct-8.19.0-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by:

[oe] [meta-python][PATCH] python3-eventlet: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the hatchling.build PEP-517 backend. Fix: WARNING: python3-eventlet-0.36.1-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with hatchling.build, use the correct class [pep517-backend] Signed-off-by: alperak ---

[oe] [meta-python][PATCH] python3-classes: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the poetry.core.masonry.api PEP-517 backend. Fix: WARNING: python3-classes-0.4.1-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with poetry.core.masonry.api, use the correct class [pep517-backend] Signed-off-by

[oe] [meta-python][PATCH] python3-lazy: switch to PEP-517 build backend

The project has a proper pyproject.toml which declares the setuptools.build.meta PEP-517 backend. Fixes: WARNING: python3-lazy-1.6-r0 do_check_backend: QA Issue: inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend] Signed-off-by: alper

[oe] how to build EXTERNAL kernel module with “inherit module externalsrc”

hi all： i have a problem。 i want build EXTERNAL kernel module and module src is outside。 just like this： “ inherit module externalsrc EXTERNALSRC:pn-x = "/xxx/source/kernel-modules" EXTERNALSRC_BUILD:pn-x = "${S}" do_compile[dirs]= "${S}" do_install[dirs]= "${S}" ” i dont want build tmp in my sour

[oe] [scarthgap][master][PATCH 2/2] libatasmart: Update SRC_URI

From: Changqing Li Update SRC_URI to fix do_fetch warning Signed-off-by: Changqing Li --- meta-oe/recipes-support/libatasmart/libatasmart_0.19.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-support/libatasmart/libatasmart_0.19.bb b/meta-oe/recipes-suppo

[oe] [scarthgap][master][PATCH 1/2] pavucontrol: update SRC_URI

From: Changqing Li Server's https certificate isn't valid for freedesktop.org without www prefix, refer [1]. Update SRC_URI to fix do_fetch warning [1] https://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/1537 Signed-off-by: Changqing Li --- meta-oe/recipes-multimedia/pulseaudio/pa

Re: [oe] [meta-networking][PATCH] blueman: skip buildpath error

INSANE_SKIP is usually set on a per-package basis. e.g., meta/recipes-support/vim/vim.inc:INSANE_SKIP:${PN}-tools = "file-rdeps" And following the link you provide, it does look like a blueman issue, because otherwise all projects using cython will have the same problem. I'm not sure about it t