https://bugs.kde.org/show_bug.cgi?id=423003
Friedrich W. H. Kossebau <kosse...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |UPSTREAM
--- Comment #52 from Friedrich W. H. Kossebau <kosse...@kde.org> ---
> Package: libkf5akonadisearch-plugins
> Version: 4:20.08.0-0xneon+20.04+focal+build11
That version might be the trigger then. Because from what I see on
https://build.neon.kde.org/job/focal_release_kde_akonadi-search_bin_amd64/11/console
this was build against unpatched KF KRunner 5.72 (seems
https://mail.kde.org/pipermail/distributions/2020-July/000427.html missed to
trigger Neon packager attention), and due to plain
"add_definitions(-DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x054800)" in
akonadi-search CMakeLists.txt brings us the original bug.
Solutions (needs Neon packagers):
a) rebuild akonadi-search package against KF KRunner 5.73 (which is fixed)
b) add fix patch to KF KRunner 5.72 and do new package, then rebuild
akonadi-search against new KRunner package with the fix
As this bug issue entry is about the bug in KRunner code itself, not moving
this whole bug to Neon, but closing it as resolve again. And instead have
opened bug https://bugs.kde.org/show_bug.cgi?id=425599, Neon users hitting this
bug now, please subscribe and follow up there.
--
You are receiving this mail because:
You are watching all bug changes.
