An example is in partitionmanager. From https://invent.kde.org/kde-linux/kde-linux-packages/-/jobs/3388699/raw: 2025-09-22T05:36:59.607893Z 01O -- Build files have been written to: /builds/kde-linux/kde-linux-packages/pkgbuilds/kde-banana-partitionmanager-git/src/build 2025-09-22T05:36:59.746591Z 01O [1/86] Generating po/sl/docs/partitionmanager/index.cache.bz2 2025-09-22T05:36:59.746601Z 01O FAILED: po/sl/docs/partitionmanager/index.cache.bz2 /builds/kde-linux/kde-linux-packages/pkgbuilds/kde-banana-partitionmanager-git/src/build/po/sl/docs/partitionmanager/index.cache.bz2 2025-09-22T05:36:59.746603Z 01O cd /builds/kde-linux/kde-linux-packages/pkgbuilds/kde-banana-partitionmanager-git/src/partitionmanager && /usr/bin/meinproc6 --check --cache /builds/kde-linux/kde-linux-packages/pkgbuilds/kde-banana-partitionmanager-git/src/build/po/sl/docs/partitionmanager/index.cache.bz2 po/sl/docs/partitionmanager/index.docbook 2025-09-22T05:36:59.746605Z 01O introduction.docbook:9: validity error : standalone: normalization of attribute linkend on glossterm by external subset declaration 2025-09-22T05:36:59.746606Z 01O > in <glossterm linkend="glossary-filesystem " This is caused by a change in Libxml 2.15.0, which became more strict: https://gitlab.gnome.org/GNOME/libxml2/-/commit/e4cbc295fa97f3c290cec8b243bd96ebdaa3dab2. Arch just rolled out Libxml 2.15.0, so Arch users are now seeing this issue. But we don't have an Arch-based CI, so it's not seen there.
It should be fixed in a few hours, fingers crossed. I've fixed master only for now, do you need the current stable branch too?
For KDE Linux, master only is fine. For the stable branch, it's probably fine if it's fixed before anyone on Arch needs to package it again, but I'm CCing Antonio who may be able to provide a better answer.
(In reply to Luigi Toscano from comment #1) > It should be fixed in a few hours, fingers crossed. I've fixed master only > for now, do you need the current stable branch too? As long as it's merged before 25.08.2, it's fine (otherwise we'd need to patch it)
Can confirm the latest commit fixed it in master. Thanks!