python3-pygobject skips itself on target unless GI_DATA_ENABLED, which also needs qemu-usermode in MACHINE_FEATURES. blueprint-compiler and python3-dbusmock only check the gobject-introspection-data DISTRO_FEATURE, so on machines without qemu-usermode (e5500/e6500, and their lib32/lib64 multilibs) world has no provider for python3-pygobject. Found with yocto-check-layer test_machine_world on meta-freescale.
Same mismatch as "gstreamer1.0-python: Skip when GI data is not available". blueprint-compiler skips on target like python3-pygobject (blueprint-compiler-native, which epiphany uses, is unaffected); python3-dbusmock only recommends python3-pygobject when GI_DATA_ENABLED, as glib's ptest already does for python3-dbusmock. Luciano Dittgen (2): blueprint-compiler: Skip on target when GI data is not available python3-dbusmock: Recommend python3-pygobject only with GI data meta/recipes-devtools/python/python3-dbusmock_0.38.1.bb | 4 ++-- .../blueprint-compiler/blueprint-compiler_0.20.4.bb | 9 ++++++++- 2 files changed, 10 insertions(+), 3 deletions(-) -- 2.54.0
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#247253): https://lists.openembedded.org/g/openembedded-core/message/247253 Mute This Topic: https://lists.openembedded.org/mt/121595449/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
