GPG errors are hard to debug about prs

[timvisee]

Thanks for your report! That's an interesting case.

I agree that gpg's output is quite sparse. That is to remove a lot of noise when operating with gpg. It's quite hard to decide what to show in what situations.

Dumping gpg's output with --verbose sounds like an easy and good solution. A GPG_ARGS variable may be useful to pass additional arguments to gpg, such as its verbosity flag. Do you think that adding these two things is sufficient?

[timvisee]

Dumping gpg output on error when --verbose is set is now implemented on the master branch.

This took a while because it required API changes, and is still somewhat limited. This currently only outputs for the gnupg-bin backend, as the gpgme backend doesn't have a stdout/stderr.

Here is an example of what is currently shown with a gpg error:

I will probably add logic to print the exact gpg command that is invoked as well, to allow easier debugging outside of prs.

I'll leave this open until this is released under a new version.

[timvisee]

I will probably add logic to print the exact gpg command that is invoked as well, to allow easier debugging outside of prs.

This is now also added:

[timvisee]

This is now released as part of v0.5.0!

I expect the information that is now shown in verbose mode to be sufficient for proper debugging.

Feel free to open the issue again if you have further input on this.