public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Dolbec" <dolsen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-keys:master commit in: gkeys-ldap/gkeyldap/
Date: Tue, 17 Mar 2015 19:51:22 +0000 (UTC)	[thread overview]
Message-ID: <1426119320.15298629aee8ae561c409718b8903726fcba330a.dolsen@gentoo> (raw)

commit:     15298629aee8ae561c409718b8903726fcba330a
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 12 00:15:20 2015 +0000
Commit:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
CommitDate: Thu Mar 12 00:15:20 2015 +0000
URL:        https://gitweb.gentoo.org/proj/gentoo-keys.git/commit/?id=15298629

gkeyldap/actions.py: Comment out longkeyid check

The keyid and longkeyid's are being removed soon.
With the fix-fp.sh script removing them, There are more and more false positives for errors.

 gkeys-ldap/gkeyldap/actions.py | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/gkeys-ldap/gkeyldap/actions.py b/gkeys-ldap/gkeyldap/actions.py
index 3f07829..7e951e0 100644
--- a/gkeys-ldap/gkeyldap/actions.py
+++ b/gkeys-ldap/gkeyldap/actions.py
@@ -242,12 +242,12 @@ class Actions(object):
         else:
             gpgkey = 'Missing or Bad fingerprint from LDAP info'
             is_good = False
-        if not keyinfo['longkeyid']:
-            self.logger.error('ERROR in ldap info for: %s, %s'
-                % (info['uid'][0], info['cn'][0]))
-            self.logger.error('  A valid keyid, longkeyid or fingerprint '
-                'was not found for %s : gpgkey = %s' % (info['cn'][0], gpgkey))
-            is_good = False
+        #if not keyinfo['longkeyid']:
+            #self.logger.error('ERROR in ldap info for: %s, %s'
+                #% (info['uid'][0], info['cn'][0]))
+            #self.logger.error('  A valid keyid, longkeyid or fingerprint '
+                #'was not found for %s : gpgkey = %s' % (info['cn'][0], gpgkey))
+            #is_good = False
         return (keyinfo, is_good)
 
 


             reply	other threads:[~2015-03-17 19:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 19:51 Brian Dolbec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-07 14:05 [gentoo-commits] proj/gentoo-keys:master commit in: gkeys-ldap/gkeyldap/ Brian Dolbec
2016-12-23 19:55 Brian Dolbec
2015-05-31  5:03 Brian Dolbec
2015-03-24  3:13 Brian Dolbec
2015-02-11 17:37 Brian Dolbec
2015-01-05 23:12 Brian Dolbec
2015-01-05 23:12 Brian Dolbec
2015-01-05 23:12 Brian Dolbec
2015-01-05 23:12 Brian Dolbec
2014-12-26 18:37 Brian Dolbec
2014-12-25 20:43 Brian Dolbec
2014-12-25 20:43 Brian Dolbec
2014-12-25 20:43 Brian Dolbec
2014-12-25 20:43 Brian Dolbec
2014-12-25 20:43 Brian Dolbec
2014-12-25 20:43 Brian Dolbec
2014-12-25 20:43 Brian Dolbec
2014-12-22 23:11 Brian Dolbec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1426119320.15298629aee8ae561c409718b8903726fcba330a.dolsen@gentoo \
    --to=dolsen@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox