Bug#771857: caff: Please support GnuPG 2.1

2015-02-20 Thread Guilhem Moulin
In fact I changed that (r773) to symlink the agent's socket(s) instead; it's much cleaner as it doesn't spawn multiple agent in ~/.caff/gnupghome and the temporary directories. However caff won't work with gpg <= 2.1.2, due to gpg not flushing its standard output before the status prompts during t

Bug#771857: caff: Please support GnuPG 2.1

2015-01-03 Thread Guilhem Moulin
Following http://lists.gnupg.org/pipermail/gnupg-devel/2015-January/029301.html caff's $CONFIG{'secret-keyring'} has been deprecated, and the symlinks are automatically created when the secret keyrings are not present. -- Guilhem. signature.asc Description: Digital signature

Bug#771857: caff: Please support GnuPG 2.1

2014-12-29 Thread Guilhem Moulin
This is due to GnuPG 2.1 ignoring --secret-keyring: --secret-keyring file This is an obsolete option and ignored. All secret keys are stored in the private-keys-v1.d directory below the GnuPG home directory. But caff has its own GnuPG home (~/.caff/gnupghome by defaul