Re: Did exit codes change in 2.1.21?

Hej, > Here is my fix: > https://dev.gnupg.org/rGa8dd96826f8484c0ae93c954035b95c2a75c80f2 > > Please try this patch. seems to work. Now the exit code is 0 again, as expected. When building without SCDAEMON support, I get gpg: WARNING: server 'scdaemon' is older than us ((null) < 2.1.21)

Re: Did exit codes change in 2.1.21?

Philip Jocks wrote: > gpg: error getting version from 'scdaemon': Not supported > [GNUPG:] CARDCTRL 6 This is due to my badness. I wrongly assumed everyone uses smartcard. :-) > Is there anything else we can try? Here is my fix:

Did exit codes change in 2.1.21?

Hi, we're using duply/duplicity with gnupg on FreeBSD and upgraded a few machines to gnupg 2.1.21 yesterday. That made the backups stop working, as some selftest doesn't work. Running this: echo "passphrase" | gpg --sign --default-key --passphrase-fd 0 --batch -r -r