From 5d81ca7d29f17e6ed64332597422f09cb9f651a3 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" Date: Sun, 27 Apr 2014 14:58:33 +0000 Subject: [PATCH] --- ...ypt_based_repos_and_conflicting_uuids.mdwn | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn new file mode 100644 index 0000000000..bc8fb12e16 --- /dev/null +++ b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn @@ -0,0 +1,23 @@ +### Please describe the problem. + +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. + +### What steps will reproduce the problem? + + +### What version of git-annex are you using? On what operating system? + + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]]