Michael Weiss f76c842706 gpgme: 1.10.0 -> 1.11.1 ... I've rebuild all packages that depend on gpgme and everything seems fine so far (there are a few failures but the ones I've checked are unrelated to gpgme). Upstream release notes (Noteworthy changes in version 1.11.1): * Fixed build problems in the 1.11.0 release. * Added C++ interfaces which were planned for 1.11.0. The 1.11.0 release came with these changes: * New encryption API to support direct key specification including hidden recipients option and taking keys from a file. This also allows to enforce the use of a subkey. * New encryption flag for the new API to enforce the use of plain mail addresses (addr-spec). * The import API can now tell whether v3 keys are skipped. These old and basically broken keys are not anymore supported by GnuPG 2.1. * The decrypt and verify API will now return the MIME flag as specified by RFC-4880bis. * The offline mode now has an effect on gpg by disabling all network access. [#3831] * A failed OpenPGP verification how returns the fingerprint of the intended key if a recent gpg version was used for signature creation. * New tool gpgme-json as native messaging server for web browsers. As of now public key encryption and decryption is supported. Requires Libgpg-error 1.29. * New context flag "request-origin" which has an effect when used with GnuPG 2.2.6 or later. * New context flag "no-symkey-cache" which has an effect when used with GnuPG 2.2.7 or later. * New convenience constant GPGME_KEYLIST_MODE_LOCATE. * Improved the Python documentation. * Fixed a potential regression with GnuPG 2.2.6 or later. * Fixed a crash in the Python bindings on 32 bit platforms. [#3892] * Various minor fixes.		2018-04-21 23:25:14 +02:00
..
default.nix	gpgme: 1.10.0 -> 1.11.1	2018-04-21 23:25:14 +02:00
gpgme_libsuffix.patch