After the update to 2.1.10, I see a bogus "ambiguous" report:

% gpg --list-keys rickert
gpg: key specification 'D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1' is ambiguous
gpg: (check argument of option '--encrypt-to')
gpg: 'D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1' matches at least:
gpg: D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1
gpg: D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1

It seems to say that a key is ambiguous with itself.

A one-line change to my options file seems to eliminate the error:

43c43

< encrypt-to D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1

encrypt-to 0x46B1EFE1

With that change, I am still specifying the same "encrypt-to" key. To me, this
looks like a bug in the handling of options. That I used the most unambiguous
way of specifying the key should not trigger an "ambiguous key" error.