Created attachment 871381 [details] My .caffrc Description of problem: When I run caff to sign a key and send mail, I get an endless loop complaining about unable to import key into temporary gnupg. An example session looks like: """ simon@localhost:~$ caff 16cd1479 defined(@array) is deprecated at /bin/caff line 599. (Maybe you should just omit the defined()?) [INFO] Importing key 50E5C9F6F2E084D6 from your normal GnuPGHome. [INFO] fetching keys, this will take a while... [INFO] Sign the following keys according to your policy, then exit gpg with 'save' after signing each key gpg --homedir=/home/simon/.caff/gnupghome --secret-keyring /home/simon/.gnupg/secring.gpg --no-auto-check-trustdb --trust-model=always --edit ADF85A24A73E95DFED2756A0C4424E8716CD1479 sign gpg (GnuPG) 1.4.16; Copyright (C) 2013 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. pub 4096R/16CD1479 created: 2013-06-11 expires: never usage: SC sub 4096R/FE1406FD created: 2013-06-11 expires: 2014-06-11 usage: S sub 4096R/FF2AF0E9 created: 2013-06-11 expires: 2014-06-11 usage: E sub 4096R/8FAC6DD6 created: 2013-06-11 expires: 2014-06-11 usage: A [ unknown] (1). Thomas Jepp <tom.uk> [ unknown] (2) Thomas Jepp <tom> [ unknown] (3) Thomas Jepp <reg.uk> [ unknown] (4) Thomas Jepp <admin.uk> [ unknown] (5) Thomas Jepp <minimaul> Really sign all user IDs? (y/N) y pub 4096R/16CD1479 created: 2013-06-11 expires: never usage: SC Primary key fingerprint: ADF8 5A24 A73E 95DF ED27 56A0 C442 4E87 16CD 1479 Thomas Jepp <tom.uk> Thomas Jepp <tom> Thomas Jepp <reg.uk> Thomas Jepp <admin.uk> Thomas Jepp <minimaul> Are you sure that you want to sign this key with your key "Simon Farnsworth (Home) <simon.uk>" (F2E084D6) Really sign? (y/N) y You need a passphrase to unlock the secret key for user: "Simon Farnsworth (Home) <simon.uk>" 4096-bit RSA key, ID F2E084D6, created 2012-01-25 gpg> save Could not import ADF85A24A73E95DFED2756A0C4424E8716CD1479 into temporary gnupg. Could not import ADF85A24A73E95DFED2756A0C4424E8716CD1479 into temporary gnupg. """ Where the "Could not import" repeats endlessly Version-Release number of selected component (if applicable): pgp-tools-1.1.4-3.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Run caff with a keyid on the command line. 2. See failure as in session above Actual results: Endless "could not import" loops Expected results: Mail sent to key owner with a signature. Additional info: I'm going to attach my .caffrc in case that's the problem.
I've just tried upstream's 1.15 from tarball, and that worked. Any chance of an updated package?
Same problem here. Fedora 20 x86_64 I also found this thread [1] on the gnupg-devel list wich seems related. [1] http://lists.gnupg.org/pipermail/gnupg-devel/2014-January/028140.html
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.