Bug 440177

Summary: no kconf_update5 support on binary factory
Product: [Developer tools] Craft Reporter: Ralf Habacker <ralf.habacker>
Component: BlueprintsAssignee: Hannah von Reth <vonreth>
Status: RESOLVED FIXED    
Severity: normal CC: kde-windows, kloecker
Priority: NOR    
Version: stable   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Bug Depends on:    
Bug Blocks: 426400    

Description Ralf Habacker 2021-07-23 08:00:26 UTC
SUMMARY
The snapshots from the KDE binary factory do not provide support for updating configuration files. Configuration file updates are automatically provided by kded5 using kconf_update5, see https://techbase.kde.org/Development/Tutorials/Updating_KConfig_Files#How_it_works. Both applications are not included in the snapshots. 

STEPS TO REPRODUCE
1. download portable kmymoney binary snapshot from https://binary-factory.kde.org/job/KMyMoney_Release_win64/
2. unpack archive
3. inspect the bin dir

OBSERVED RESULT
In the bin directory kded5.exe and kconf_update5.exe is missing

EXPECTED RESULT
The mentioned executables should be included in the snapshots

SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 5.84
Qt Version: 5.15
Comment 1 Ingo Klöcker 2022-09-13 14:22:16 UTC
kded is Linux/FreeBSD-only. As written on the page you linked you can start kconf_update manually using `KConfig::checkUpdate()`. Of course, kconf_update.exe still needs to be packaged by craft.
Comment 2 Ingo Klöcker 2022-09-13 15:51:14 UTC
Git commit c726dc3f0cdcf6f9a632910b90840c6725e5c6fd by Ingo Klöcker, on behalf of Ingo Klöcker.
Committed on 13/09/2022 at 15:50.
Pushed by kloecker into branch 'master'.

kmymoney: Do not blacklist kconf_update.exe

M  +1    -1    extragear/kmymoney/blacklist.txt

https://invent.kde.org/packaging/craft-blueprints-kde/commit/c726dc3f0cdcf6f9a632910b90840c6725e5c6fd
Comment 3 Ingo Klöcker 2022-09-13 15:55:59 UTC
kconf_update.exe should now be included in the kmymoney installers, but I couldn't test it because kmymoney doesn't build on binary factory since the update of libofx.

As written before it's now your responsibility in kmymoney to actually apply kmymoney's config updates with appropriate calls of `KConfig::checkUpdate()` for the Windows (and macOS) builds.