I have installed app-crypt/gkeys-0.2 (but the same occured with -9999). In my /etc/gitconfig I have the entry: [gpg] program = gkeys-gpg When doing in the gentoo repository git log --show-signature I see instead of verified signatures: Traceback (most recent call last): File "/usr/lib/python-exec/python3.4/gkeys-gpg", line 62, in <module> returncode = main() File "/usr/lib64/python3.4/site-packages/gkeysgpg/cli.py", line 65, in __call__ args = self.parse_args(sys.argv[1:]) File "/usr/lib64/python3.4/site-packages/gkeys/base.py", line 248, in parse_args self._add_options(parser, self.cli_config['Base_Options']) File "/usr/lib64/python3.4/site-packages/gkeys/base.py", line 283, in _add_options getattr(self, '_option_%s' % opt)(parser) File "/usr/lib64/python3.4/site-packages/gkeys/base.py", line 223, in _option_uid help='The user ID, gpg key uid') File "/usr/lib64/python3.4/argparse.py", line 1349, in add_argument return self._add_action(action) File "/usr/lib64/python3.4/argparse.py", line 1709, in _add_action self._optionals._add_action(action) File "/usr/lib64/python3.4/argparse.py", line 1553, in _add_action action = super(_ArgumentGroup, self)._add_action(action) File "/usr/lib64/python3.4/argparse.py", line 1363, in _add_action self._check_conflict(action) File "/usr/lib64/python3.4/argparse.py", line 1502, in _check_conflict conflict_handler(action, confl_optionals) File "/usr/lib64/python3.4/argparse.py", line 1511, in _handle_conflict_error raise ArgumentError(action, message % conflict_string) argparse.ArgumentError: argument -u/--uid: conflicting option string: -u
Still no news on this, even on the live version. The problem seems to be rather clear: The same option -u is used twice for different purposes $ grep -- "'-u'" /usr/lib64/python3.5/site-packages/gkeys*/*.py /usr/lib64/python3.5/site-packages/gkeys/base.py: parser.add_argument('-u', '--uid', dest='uid', nargs='+', default=None, /usr/lib64/python3.5/site-packages/gkeysgpg/cli.py: parser.add_argument('-u', '--local-user', dest='user', default=None, However, changing -u to -U in either of the 2 occurrences leads to other error messages. My guess is that internally -u is actually used in the two colliding ways somehow.
This error still persists in latest master
app-crypt/gkeys is last rited now.
Removing.
