I'm just going to leave this here: https://nedbatchelder.com/blog/201405/github_monoculture.html
Hey, lots of complaints here, but I'm happy you're on sr.ht. I find the increasing invasive ("validate your email" popups, PII fishing attempts) to be distasteful. While github has some nice features, it's already started to slide downhill after the Microsoft acquisition and some interactions are becoming downright annoying. The UI is starting to acquire that heavy JS bulk that makes it slower, heavier bandwidth, and twitchy, and some of the UI changes they're implementing are user hostile (I'm looking at you, Fork Insights). CI on sr.ht is objectively superior to Actions on Github. Github context menu items, mirroring the outright idiocy of MS Ribbons, is unacceptable. And Github only supports git, making it a sterile monoculture. Github is following an Eclipse-for-the-web, kitchen-sink, monolithic, bloated application suite.
I, for one, commend, support, and advocate for the clean simplicity of the sr.ht approach. I hope gio retains some sanity and resists calls to move to Github.
Oh, this could definitely be it for me too. I have had my key since 1999 and have several revoked UIDs, many which predate my current primary ID.
A quick search in the pgpy project's issue tracker didn't turn up any issues with the
is_primarymethod, so they either aren't aware of it or there's something else going on.
Can you post a snippit of the commands you used to get to your keys using
pgpyin the interpreter?
BTW, my key can be retrieved from most public keyservers; I know it's up-to-date at keys.gnupg.net. The key ID is 09E5788F. For testing:
gpg --receive-keys --keyserver keys.gnupg.net 09E5788F
In my case, it doesn't have an EC subkey; the key is DSA 1024, with ElGamal 2048 and DSA 2048 subkeys. The error I'm getting is
We were unable to encrypt a test message with this key
I don't seem to be obviously having the same issue as any of #106, #79, or #54.
The export command I'm using is:
gpg --armor --export-options export-minimal --export email@example.com
This may be another case of a gpgy bug, but filing just in case it isn't.