From d43e44e3e5667dbfae4bedaf9bca8a5f773a643c Mon Sep 17 00:00:00 2001
From: spwhitton <spwhitton@web>
Date: Thu, 17 May 2018 19:49:04 +0000
Subject: [PATCH] Added a comment: analysis

---
 ...mment_1_40b31c79eedb59e66ef34e27ed7d137d._comment | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 doc/bugs/gcrypt_repository_not_found/comment_1_40b31c79eedb59e66ef34e27ed7d137d._comment

diff --git a/doc/bugs/gcrypt_repository_not_found/comment_1_40b31c79eedb59e66ef34e27ed7d137d._comment b/doc/bugs/gcrypt_repository_not_found/comment_1_40b31c79eedb59e66ef34e27ed7d137d._comment
new file mode 100644
index 0000000000..fa0a135f81
--- /dev/null
+++ b/doc/bugs/gcrypt_repository_not_found/comment_1_40b31c79eedb59e66ef34e27ed7d137d._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="spwhitton"
+ avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb"
+ subject="analysis"
+ date="2018-05-17T19:49:04Z"
+ content="""
+\"Repository not found\" is expected when you have not yet pushed with gcrypt.
+
+I think the error is rather that git-annex is passing `--signed=if-asked` to git-remote-gcrypt and it does not like that, dies and never sets up the repository.
+
+I am not sure whether git-annex should stop passing that option, or git-remote-gcrypt should accept the option and do nothing with it.
+"""]]