SUMMARY re: Pipeline Okular_Release_win64 #1575 Nov 10, 2023 4:02 AM KDE-Okular-Win_x64 okular-23.08.2-1575-win_x64-cl-msvc2019.exe Missing file: gpgme-w32spawn.exe (missing from /bin) The sha256 is good, but the sha256 is good for an .exe that already was, and still is, missing the file needed for "Configure backends..." When gpgme-w32spawn.exe is restored to /bin, "Configure backends..." works as expected. STEPS TO REPRODUCE 1. Click on Settings, then click on "Configure backends..." 2. if Okular has just been started, error msg box appears upon step 1 2a. this error box appears just once each for each Okular session; clicking on "Configure backends..." a 2nd time brings up the config backends window. 3. only (default) font MS Shell Dlg 2 is available in the config window for each file type OBSERVED RESULT 4. Can't change font for any file type 5. Restoring a copy of gpgme-w32spawn.exe to the /bin directory restores functionality EXPECTED RESULT 6. Now able to select a new font for each type of document SOFTWARE/OS VERSIONS Windows: Windows 10 Home 22H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION https://binary-factory.kde.org/job/Okular_Release_win64/ #1575 has a blue "success" icon: okular-23.08.2-1575-win_x64-cl-msvc2019.exe was downloaded from: https://binary-factory.kde.org/job/Okular_Release_win64/
A possibly relevant merge request was started @ https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/704
Git commit 3ccb758d7388a0225c667cf34121227c8245cc80 by Hannah von Reth, on behalf of Sune Vuorela. Committed on 16/11/2023 at 14:59. Pushed by vonreth into branch 'master'. Okular: don't blacklist gpgme-w32spawn When poppler is built with gpgme support, we need the gpgme-w32spawn to be able to find a system install of gpg M +1 -1 kde/applications/okular/blacklist.txt https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/3ccb758d7388a0225c667cf34121227c8245cc80
For the record we at GnuPG realized that this was an issue that is unintentional and will remove the requirement for gpgme-w32-spawn.exe lying next to the gpgme.dll in one of the next GPGME releases. Our upstream issue for this is: https://dev.gnupg.org/T6818