[ostree] gpg: Link to GPGME bug about GPGME_SIGSUM_KEY_REVOKED

[Matthew Barnes <mbarnes src gnome org>]

commit f9e95e2cd39e23b2c420addc10917e8e3d6b7a20
Author: Matthew Barnes <mbarnes redhat com>
Date:   Thu Mar 19 10:21:08 2015 -0400

    gpg: Link to GPGME bug about GPGME_SIGSUM_KEY_REVOKED

 src/libostree/ostree-gpg-verify-result.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/src/libostree/ostree-gpg-verify-result.c b/src/libostree/ostree-gpg-verify-result.c
index 301ff91..7f4b3d8 100644
--- a/src/libostree/ostree-gpg-verify-result.c
+++ b/src/libostree/ostree-gpg-verify-result.c
@@ -97,7 +97,10 @@ signing_key_is_revoked (gpgme_signature_t signature)
    * bit on a revoked signing key but rather GPGME_SIGSUM_SYS_ERROR and the
    * status field shows GPG_ERR_CERT_REVOKED.  Turns out GPGME is expecting
    * GPG_ERR_CERT_REVOKED in the validity_reason field which would then set
-   * the summary bit.  Unsure if this is a bug, but best check for both. */
+   * the summary bit.
+   *
+   * Reported to GPGME: https://bugs.g10code.com/gnupg/issue1929
+   */
 
   return (signature->summary & GPGME_SIGSUM_KEY_REVOKED) ||
          ((signature->summary & GPGME_SIGSUM_SYS_ERROR) &&