Daniel confused --list-options with --dump-options. The linked completion script uses the latter.

Needs to be tested/verified by other developers. In short you do

./autogen.sh
cd packages
./download.sh
cd ..
./build.sh --appimage --builddir=...

If you omit the --builddir=... option then ~/b/SRCDIRNAME-appimage will be used.

Building an AppImage including Kleopatra and Okular works now (again) in the gpg4win-5-branch.

It's pretty ironic that we added DBUS_SESSION_BUS_ADDRESS because of pinentry-gnome3 and now we need to add an option to remove it because of pinentry-gnome3.

$ man gpg
       --gpgconf-list
              This command is similar to --list-config but in general only internally used by the gpgconf tool.

In general, "only internally used" means: Don't use this yourself or accept what it does.

Fixed.

In T7515#197774, @TobiasFella wrote:

I'd suggest removing:

If a single OpenPGP certificate is updated then we now show the same detailed information for the update from WKD as for the update from a keyserver, i.e. if the certificate didn't change via WKD then we say so.

I think there's some confusion.

You need to be asked this question when you restore the backup of all of your keys or when you migrate all your secret keys to a new computer.

Tested locally:

• Build the Docker image for building the AppImage (using the archived CentOS 7 packages).
• Build an AppImage for Gpg4win 4.4 with the unsplit gpgme repo.
• Build an AppImage for Gpg4win 4.4 with the split gpgme repos (T7262).

I'm not sure what Kleopatra should do differently. Kleopatra relies on the error messages provided by gpgme which in turn relies on gpg's status messages.

The wonders of Windows! Who knows which overzealous component of Windows deleted this file. I suspect that your virus scanner wrongly suspected the file to be malicious (false positive) and removed it. Kleopatra certainly doesn't delete any of its files itself unless you uninstall it. Since a reinstallation (as proposed by Windows likely because vanishing files is a common problem on Windows) solved your problem I'll close this ticket as resolved.