| Message ID | 20240116110814.1052866-1-alex@linutronix.de |
|---|---|
| State | Accepted, archived |
| Commit | c9010feb8e4862f5c0dfde33ba73f3e7cc35b790 |
| Headers | show |
| Series | [v2,1/3] glib-2.0: ensure GI_DATA_ENABLED is set | expand |
diff --git a/meta/recipes-core/glib-2.0/glib.inc b/meta/recipes-core/glib-2.0/glib.inc index ae6fc519922..5a57549d855 100644 --- a/meta/recipes-core/glib-2.0/glib.inc +++ b/meta/recipes-core/glib-2.0/glib.inc @@ -28,7 +28,7 @@ PACKAGES += "${PN}-codegen ${PN}-utils" LEAD_SONAME = "libglib-2.0.*" -inherit meson gettext gtk-doc pkgconfig ptest-gnome upstream-version-is-even bash-completion gio-module-cache manpages +inherit meson gettext gtk-doc pkgconfig ptest-gnome upstream-version-is-even bash-completion gio-module-cache manpages gobject-introspection-data GTKDOC_MESON_OPTION = "gtk_doc"
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 by glib recipe subject to GI_DATA_ENABLED, and that variable is not global but defined in a g-i-data class that glib recipe did not include. So needed dependencies were simply always excluded regardless of g-i settings, until now. Signed-off-by: Alexander Kanavin <alex@linutronix.de> --- v2: include g-i-data class instead of depending on python3-dbusmock unconditionally; that didn't actually work --- meta/recipes-core/glib-2.0/glib.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)