aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2018-03-02 13:05:08 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2018-03-02 13:05:08 -0400
commit17029c18af9723d96426bfd918661cd576558e66 (patch)
treee5e3bd8d130343be242c167e80e0898e74347357
parent03cd2970ad9762511fc522168926a8d8ea7fdc94 (diff)
parentda1c087169d083d8af0e24f0e7190dc3002603b6 (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
-rw-r--r--doc/forum/Adding_public_key_to_hybrid_encrypted_repo_causes___34__remote_already_exists__34___error.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/Adding_public_key_to_hybrid_encrypted_repo_causes___34__remote_already_exists__34___error.mdwn b/doc/forum/Adding_public_key_to_hybrid_encrypted_repo_causes___34__remote_already_exists__34___error.mdwn
new file mode 100644
index 000000000..8032584f1
--- /dev/null
+++ b/doc/forum/Adding_public_key_to_hybrid_encrypted_repo_causes___34__remote_already_exists__34___error.mdwn
@@ -0,0 +1,5 @@
+Hello, I'm running git-annex version: 5.20151208-1build1. I am trying to add a public key to my git annex repo but it tells me the repo already exists. I worked around this by marking the repo as dead and re-enabling but I feel like this isn't the correct course of action. Is there another way to avoid this error?
+
+ $ git annex enableremote annex.repo keyid+=920D7A56
+ enableremote annex.repo (encryption update) (hybrid cipher with gpg keys 97A273201BA73A76 A50E9160920D7A56) fatal: remote annex.repo already exists.
+ git-annex: git [Param "remote",Param "add",Param "annex.repo",Param "gcrypt::ssh://ben@annex/dataset/annex/share"] failed