From 17782b53a17f87956d79cb332ca57a0b91ca55c8 Mon Sep 17 00:00:00 2001 From: "bwong@047cc3a313979f155ea3d7ea765358b92116e045" Date: Thu, 1 Mar 2018 01:35:31 +0000 Subject: [PATCH 1/2] adding public keys to hybrid encryption remote --- ..._repo_causes___34__remote_already_exists__34___error.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/forum/Adding_public_key_to_hybrid_encrypted_repo_causes___34__remote_already_exists__34___error.mdwn 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 0000000000..62df8869af --- /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 From f1f2db703045d48454ebf1c6f26c3ceb3dfd67e6 Mon Sep 17 00:00:00 2001 From: "bwong@047cc3a313979f155ea3d7ea765358b92116e045" Date: Thu, 1 Mar 2018 01:36:57 +0000 Subject: [PATCH 2/2] --- ...repo_causes___34__remote_already_exists__34___error.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 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 index 62df8869af..8032584f1e 100644 --- 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 @@ -1,5 +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 + $ 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