mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

response

Browse source
This commit is contained in:
Joey Hess 2016-10-05 15:50:50 -04:00
parent 34530e59d9
commit 3a019c5050
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 32 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
doc/forum/uuid_mismatch___59___expected_Just___40__UUID_...___41___but_remote_gitrepo_has_UUID_.../comment_1_ed29dcf70b916bdd094015c1c9616550._comment Normal file
View file

@ -0,0 +1,32 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-10-05T19:30:48Z"
content="""
It would help if you described what command you ran, or buttons you clicked
on to get this to happen. Otherwise, I'm left making a lot of guesses..
It looks like you might be running `git-annex enableremote` of a gcrypt
special remote that you set up earlier.
It appears that the gcrypt remote has a gcrypt-id which is not the same as
the one that was used when that special remote was originally initialized.
I don't know why this would happen, and without details about what you did,
I can barely venture a guess. All I can say is that, gcrypt is supposed to
pick a gcrypt-id the first time a gcrypt remote is used, and not change it
afterwards.
... It might be that you did something that caused gcrypt to pick a new
gcrypt-id.
... It might be that the special remote has been pointed at a different
gcrypt repository than the one that it was initially set up to use.
It might help to look at both the local repository's `.git/config`, and the
gcrypt git repositories git config, and see which of
them have the wrong gcrypt-id value of ":id:SCPxErEQVlqp+Hl6Su0f".
If only the local .git/config has that value and the gcrypt git repository
has some other gcrypt-id, then the other one is probably the right one, and
it might work to replace the wrong one with the right one.
"""]]