Seb, by the way, appstream-glib will probably cause several packages to FTBFS because the new version has increased the validation requirements. So projects blindly running `appstream-util validate` in their test suite may need to be updated. One workaround is to use `appstream-util validate-relax` but actually fixing the AppStream metadata is better.
Seb, by the way, appstream-glib will probably cause several packages to FTBFS because the new version has increased the validation requirements. So projects blindly running `appstream-util validate` in their test suite may need to be updated. One workaround is to use `appstream-util validate-relax` but actually fixing the AppStream metadata is better.
I found a project today, gpaste, which got the appstream validation test "for free" by using the @APPSTREAM_ XML_RULES@ autotools macro from https:/ /github. com/hughsie/ appstream- glib/blob/ master/ data/appstream- xml.m4 . See https:/ /bugs.debian. org/941731