From dcb7a8b3a95946743d71665cd4806e3af9b386ed Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" Date: Sun, 27 Apr 2014 15:09:40 +0000 Subject: [PATCH] --- doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn index bc8fb12e16..d45dcdc9cb 100644 --- a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn +++ b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn @@ -4,7 +4,7 @@ I've setup a gcrypt based git backup repository as per the examples here: http://git-annex.branchable.com/tips/fully_encrypted_git_repositories_with_gcrypt/ -It all seems to work well until I try to do any kind git annex operation from the console on the gcrypted repo on the remote server. If I run a `git annex info` (this seems a reasonable thing to do) then it initialises the encrypted remote with a different uuid to the one in the creation step. The initial repository that created the repo seems to work okay but it's no longer possible to add further repositories without getting conflicting uuid errors. +It all seems to work well until I try to do any kind git annex operation from the console on the gcrypted repo on the remote server. If I run a `git annex fsck` (this seems a reasonable thing to do) then it initialises the encrypted remote with a different uuid to the one in the creation step. The initial repository that created the repo seems to work okay but it's no longer possible to add further repositories without getting conflicting uuid errors. ### What steps will reproduce the problem?