summaryrefslogtreecommitdiff
path: root/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment
blob: e898617301f5cbf17c024fdf1988742bd9369934 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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".
"""]]