Hi Santiago,
I believe this is related to one of koko's build-dependencies
(kquickimageeditor) being uploaded
to sid [1] just before your building attempt (Dec,13th vs Dec,14th when I
understand correctly).
At the time of the build attempt, koko was at Qt5 version (23.08.5), while
kquickimageeditor was
already at Qt6 version (0.4.0). Outcome of this is what is shown in your log
-- qmlplugindump failed for org.kde.kquickimageeditor.
-- Could NOT find org.kde.kquickimageeditor-QMLModule (missing:
org.kde.kquickimageeditor-QMLModule_FOUND)
CMake Warning at
/usr/share/cmake-3.31/Modules/CMakeFindDependencyMacro.cmake:76 (find_package):
Could not find a configuration file for package "Qt5Core" that is
compatible with requested version "6.6.0".
The following configuration files were considered but not accepted:
/usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake, version:
5.15.15
/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake, version: 5.15.15
Yesterday [2] the Qt6 version (24.08.3) version of koko was uploaded to sid,
then I expect
this FTBFS to be solved now.
Looking at reproducible-builds log [3] seems also to confirm this analysis
(let's ignore armhf
for now, I've seen a lot of Plasma packages failing on that architecture
recently): build failed
on Dec,14th for koko_23.08.5, while it built reproducibly today for
koko_24.08.3 .
Is there another build attempt planned on your side, in order to confirm this
bug to be solved,
so that koko can migrate to trixie in a few days?
Thank you
Marco
[1]https://tracker.debian.org/news/1593898/accepted-kquickimageeditor-040-3-source-into-unstable/
[2]https://tracker.debian.org/news/1595574/accepted-koko-24083-1-source-into-unstable/
[3]https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/koko.html
