From 596a2eb0508123a73fdb035b841b8e8b79231b27 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 2 Jun 2016 13:20:14 -0400 Subject: analysis --- .../comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment (limited to 'doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment') diff --git a/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment b/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment new file mode 100644 index 000000000..e89861730 --- /dev/null +++ b/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment @@ -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". +"""]] -- cgit v1.2.3