From: Deepak Rathore <[email protected]> Some SDK dependency chains require python3-future to be available as SDK artifacts. The current metadata only partially provides this, which can lead to dependency resolution failures when this recipe is pulled into SDK-oriented builds.
This change does not alter target package behavior; it only enables required nativesdk variant for build and SDK integration paths. Signed-off-by: Deepak Rathore <[email protected]> --- meta-python/recipes-devtools/python/python3-future_1.0.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-python/recipes-devtools/python/python3-future_1.0.0.bb b/meta-python/recipes-devtools/python/python3-future_1.0.0.bb index eb66a7d33c..d11b560644 100644 --- a/meta-python/recipes-devtools/python/python3-future_1.0.0.bb +++ b/meta-python/recipes-devtools/python/python3-future_1.0.0.bb @@ -9,4 +9,4 @@ PYPI_PACKAGE_HASH = "99abde815842bc6e97d5a7806ad51236630da14ca2f3b1fce94c0bb94d3 inherit pypi setuptools3 -BBCLASSEXTEND = "native" +BBCLASSEXTEND = "native nativesdk" -- 2.35.6
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#125229): https://lists.openembedded.org/g/openembedded-devel/message/125229 Mute This Topic: https://lists.openembedded.org/mt/118327830/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
