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

analysis

Browse source
This commit is contained in:
Joey Hess 2016-06-02 13:20:14 -04:00
parent 64e844e1fe
commit eff6e8b1f7
Failed to extract signature
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-06-02T17:10:48Z"
content="""
What's going on here is, you have cloned a gcrypt repository so have it as
the origin remote. git-annex is storing files in that remote as if it were
a regular git remote. It's not being used as a special remote at all.
This is surely a bug; git-annex should notice that remote has a gcrypt-id
and treat it as a gcrypt remote, or refuse to use it since it's not set up
as a special remote.
It also seems that only git annex sync --content behaves this way;
git annex copy "cannot determine uuid for origin".
"""]]