blob: 41122f8a629e0d9730a6ce9ab5a52b460ea9fe07 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|
### 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 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?
### 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.
"""]]
> [[fixed|done]]; <>. I have updated the OSX autobuilder so tonight's
> build will include the fixed git-remote-gcrypt. --[[Joey]]
>
> Note that gcrypt repositories affected by this bug are in fact empty, so
> the first time a push is made with the fixed gcrypt it will probably
> generate a new gcrypt-id and push everything.
|
