Bug#771857: caff: Please support GnuPG 2.1

[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 the pruning.  This bug has already been
fixed upstream, see

  http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=d2a70fd8


-- 
Guilhem.


signature.asc
Description: Digital signature

Bug#771857: caff: Please support GnuPG 2.1

[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

[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 default), and
there is currently no configuration option to specify
‘~/.gnupg/private-keys-v1.d’ as the location for private keys.  I'll
file a wishlist bug for that.  A dirty fix in the meantime is to symlink
the directory:

rmdir ~/.caff/gnupghome/private-keys-v1.d
ln -s ~/.gnupg/private-keys-v1.d ~/.caff/gnupghome

-- 
Guilhem.


signature.asc
Description: Digital signature