From c49e002a137ba3939d4cd08b1786f1412dc35c0e Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" Date: Tue, 29 Apr 2014 09:59:53 +0000 Subject: [PATCH] --- ...multiple_remotes_syncing_to_gcrypt_based_ssh_repo_.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/forum/trouble_with_multiple_remotes_syncing_to_gcrypt_based_ssh_repo_.mdwn diff --git a/doc/forum/trouble_with_multiple_remotes_syncing_to_gcrypt_based_ssh_repo_.mdwn b/doc/forum/trouble_with_multiple_remotes_syncing_to_gcrypt_based_ssh_repo_.mdwn new file mode 100644 index 0000000000..95cfe25389 --- /dev/null +++ b/doc/forum/trouble_with_multiple_remotes_syncing_to_gcrypt_based_ssh_repo_.mdwn @@ -0,0 +1,7 @@ +Hi, + +Is anyone having difficulties with the assistant and gpg-agent? Particularly with multiple repos syncing to a crypt backup? + +It seems to work for a while and then according to the error logs I can't decrypt the manifest...I'm wondering if there is some sort of locking involved that only lets one repo sync to a gcrypt repo at a time? I can't think why the gpg-agent would stop providing the key. + +I also have a rather horrible time with gpg-agent in general: I now start each repos git annex assistant individually in the shell (from which I can confirm the gpg-agent is working) rather than launch the web-app direct.