Andrej Schoeke
Andrej Schoeke
It seems like this issue is not related to UIDs. It seems like this happens in all encrypt steps now. Maybe related to #471? Help would be appreciated.
I deleted 2.0.10 and installed 2.0.9, but the errors persist.
I tested gpgme down to 2.0.4 which is the lowest version in my repositories. The error persists across all versions. I also tested --use-system-libraries for 2.0.4 but no change.
So, I think the issue arises from ruby gpgme in combination with GPGME 1.6.0. The ruby source code showed changes to "expose new API". I am not sure if this...
Unfortunately, I can't. I installed gpgme with brew and the only version I can find there is the most current. The gpgme ruby gem in 2.0.10 exposes a new API...
I ran `rake test` on the dev version and everything came back fine, but I can't test encrypt in this version, as it crashes for me.
I checked the release branch, where the error simply is the same and `rake test` does not show any problems. However, I still get the same errors when running that...
No. None of my keys are expired. Error message for encrypt: `Problem sending mail: Exception in GPGME call: General error`, not asking me for my passphrase. Error message for sign...
The keys work "manually". I have no problems doing everything on the CLI and then copying it into a mail.
Yes, I am using this one. However, it is not expired. It expires in 2017. I am not sure why the keys on the server show a wrong date. Let...