Log message:
this gpgme wants gpgrt_calloc etc that are introduced with libgpg-error 1.28

Log message:
*: Move SUBST_STAGE from post-patch to pre-configure

Performing substitutions during post-patch breaks tools such as mkpatches,
making it very difficult to regenerate correct patches after making changes,
and often leading to substituted string replacements being committed.

Log message:
gpgme: updated to 1.11.1

version 1.11.1:
* Fixed build problems in the 1.11.0 release.
* Added C++ interfaces which were planned for 1.11.0.

version 1.11.0:
* 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.
* 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.
* Various minor fixes.

Log message:
gpgme: Improve style and comment in options.mk (NFCI)

- Move the CONFIGURE_ARGS in the `gnupg1' logic after DEPENDS to make the
  two branches symmetric
- Adjust the comment, the tests needs gpgsm, not gpg-agent

Suggested via a private email by <uwe>, thanks!

Log message:
gpgme: Disable tests that needs gpg-agent when built with gnupg1 option

When building with the gnupg1 option some tests force the need of
gpg-agent and fails as noticed by <uwe> via PR pkg/53160.

Adjust options.mk accordingly disabling gpgsm tests for the gnupg1
option.

Should fix PR pkg/53160 reported by <uwe>.

Log message:
Revert PKGNAME change from gnupg2 to gnupg

Log message:
gpgme: updated to 1.10.0

Noteworthy changes in version 1.10.0:
 * Now returns more specific error codes for decryption to distinguish
   between bad passphrase, user canceled, and no secret key.
 * Now returns key origin information if available.
 * Added context flag "auto-key-retrieve" to selectively enable the
   corresponding gpg option.
 * Added flag is_de_vs to decryption and verify results.
 * py: Use SEEK_SET as default for data.seek.
 * cpp: Various new APIs.
 * Reduced spawn overhead on Linux again.  Added new configure option
   --disable-linux-getdents to disable this feature for very old
   Linux versions.
 * Improved the Python bindings build system.
 * Made the test suite less fragile.

Log message:
Add commented out test environment flag for more detailed output.

Log message:
Fix pattern.

Log message:
Remove unnecessary comment.