Control: retitle -1 kmouth: FTBFS: "The list of supported platorms is ''" (empty) Control: tags -1 + fixed-upstream Control: forwarded -1 https://invent.kde.org/accessibility/kmouth/-/commit/cfb889ab38befe1e378d92ab9915aed14ec5843b
On Thu, 26 May 2022 at 21:06:48 +0200, Lucas Nussbaum wrote: > Relevant part (hopefully): > > CMake Error at /usr/share/ECM/kde-modules/KDEMetaInfoPlatformCheck.cmake:24 > > (file): > > file STRINGS file "/<<PKGBUILDDIR>>/metainfo.yaml" > > cannot be read. ... > > CMake Error at /usr/share/ECM/kde-modules/KDEMetaInfoPlatformCheck.cmake:69 > > (message): > > Your current platform 'Linux' is not supported. The list of supported > > platorms is ''. This appears to be happening because kmouth is using the KDEFrameworkCompilerSettings CMake module, which is only meant to be used by modules that are part of the KDE Framework (as opposed to KDE apps outside the framework), and has some assumptions that are only true for KDE Framework modules. In particular, since a few months ago, KDEFrameworkCompilerSettings assumes that all the modules it is used in will have a ./metainfo.yaml describing the project, and reports an error if you try to build on a platform not listed as supported in that file: https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/245 KDE Framework modules *do* have a ./metainfo.yaml, but kmouth does not, leading to this build failure. Newer versions of kmouth use KDECompilerSettings instead of KDEFrameworkCompilerSettings, which presumably does not have this metainfo.yaml check: https://invent.kde.org/accessibility/kmouth/-/commit/cfb889ab38befe1e378d92ab9915aed14ec5843b I hope that applying that change (or upgrading to a newer upstream release) would resolve this FTBFS. smcv
