From 287e89ea4c29b80dcb4cec0e1afd986e76987754 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 14 Jul 2014 20:15:07 +0000 Subject: Added a comment --- .../comment_4_c5e9843a956984efd22bad629930f6bd._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Moved_files_are_not_picked_up_by_the_assistant_on_OS_X/comment_4_c5e9843a956984efd22bad629930f6bd._comment (limited to 'doc/bugs') diff --git a/doc/bugs/Moved_files_are_not_picked_up_by_the_assistant_on_OS_X/comment_4_c5e9843a956984efd22bad629930f6bd._comment b/doc/bugs/Moved_files_are_not_picked_up_by_the_assistant_on_OS_X/comment_4_c5e9843a956984efd22bad629930f6bd._comment new file mode 100644 index 000000000..a437142af --- /dev/null +++ b/doc/bugs/Moved_files_are_not_picked_up_by_the_assistant_on_OS_X/comment_4_c5e9843a956984efd22bad629930f6bd._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.2" + subject="comment 4" + date="2014-07-14T20:15:07Z" + content=""" +Well, I don't see the \"??\" that you were talking about before in your transcript. I do not understand why the file's status shows as \"D\" which means it's deleted. What does `git ls-files` say? Does this stange behavior persist if you stop the assistant from running and re-run the same git-annex commands? +"""]] -- cgit v1.2.3 From 74ae7ae611c71ea0f4f0b96e6ac30607de45651c Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 14 Jul 2014 20:54:32 +0000 Subject: Added a comment --- .../comment_1_584390159278577da78b05bc7bb0e673._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment (limited to 'doc/bugs') diff --git a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment new file mode 100644 index 000000000..01b9726a9 --- /dev/null +++ b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.2" + subject="comment 1" + date="2014-07-14T20:54:32Z" + content=""" +AFAICs, this is a known bug in git-remote-gcrypt: + +In your log, it encrypts to A1FE7E9BECB5C7CA. I think this is the new key that git-annex generated. The problem comes when trying to decrypt the manifest, then it tries every gpg key until it finds one that works. +"""]] -- cgit v1.2.3