Marcus, please check this.

libtool problem. No responses for 3 months.

We won't do that for security reasons and due to other ways
of providing a passphrase (cf. gpg-agent,
gpg-preset-passphrase). No reponse for 3 months either.

Another way to use make use of an environment variable is by wrtinig an appropriate passpharse callback for gpgme.

Outdated versions and no more responses for 3 months.

Outdated versions and no response for a year.

No confirmation of fix for 3 months, so closing

Cryptplug is discontinued. Kmail now accesses GPGME directly.
Thanks for your contribution!

I think those problems have been fixed in the meantime. Can you confirm that using the latest version? Thanks.

Is this still an issue for you with the latest versions of everything? If yes, please provide the config.log file and relevant output.

Do you think gpg-agent and its passphrase-caching is adequate? You can even pre-store the passphrase on startup and never expire it. I think this is a much better solution. Please let me know if you still see the need for this feature given the superiority and completeness of gpg-agent.

I think the first problem - missing -Wl, must be reported to the libtool maintainer, and fixed in libtool proper. Then if you let us know which version of libtool fixes it, we can update the included libtool and bump up the libtool requirement.

This was fixed in GPGME 1.0.1. Thanks for your contribution!

Upgrade to a stable version

Please run the tests after setting

too old - IIRC, server hardware defect. Please don't report
such problem using the BTS.

0.3.x not continued except for security bugs. If the bug
persists in 0.3.16 using the new (gnupg 1.9.x) backend,
please report again.

Fixed a long time ago - please do not enter CVS problems
into the BTS but report them on the ML. Thanks, -wk

The 0.3.x series is no longer maintained - please update to
0.4.x and report again if the problem still persists.

Assigned

Forgot to set the category.