| Message ID | 20240112124141.433256-1-alex@linutronix.de |
|---|---|
| State | New |
| Headers | show |
| Series | [1/2] glib-2.0: pull in python3-dbusmock unconditionally | expand |
diff --git a/meta/recipes-core/glib-2.0/glib.inc b/meta/recipes-core/glib-2.0/glib.inc index ae6fc519922..9562bc23ebb 100644 --- a/meta/recipes-core/glib-2.0/glib.inc +++ b/meta/recipes-core/glib-2.0/glib.inc @@ -175,7 +175,7 @@ RDEPENDS:${PN}-ptest += "\ ${PN}-locale-th \ python3-core \ python3-modules \ - ${@bb.utils.contains('GI_DATA_ENABLED', 'True', 'python3-dbusmock', '', d)} \ + python3-dbusmock \ ${PN}-codegen \ locale-base-de-de \ locale-base-es-es \
With python 3.12 some of the glib ptests started failing. Inspection revealed that they fail because all tests in some glib's test suites are skipped; python 3.12's unittest module deems "no tests in a test suite were executed" a failure (and I tend to agree). Why are all the tests skipped? Because python dbus module is missing from the image, and it's missing because it's pulled in by dbusmock, which in turn is missing because it is pulled in subject to GI_DATA_ENABLED, and that variable is not global but defined in a g-i class that glib does not include and never did. So it was simply always excluded regardless of g-i settings. Back when this condition was added python3-dbusmock wouldn't build without introspection data enabled; now it does, so we can again pull it into ptest dependencies without conditions. Signed-off-by: Alexander Kanavin <alex@linutronix.de> --- meta/recipes-core/glib-2.0/glib.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)