From 36e9e531606460d458d9aa033f31a5d77aec884f Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 19 May 2014 16:28:01 +0000 Subject: [PATCH] Added a comment --- ...mment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment new file mode 100644 index 0000000000..d40c435db6 --- /dev/null +++ b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="216.145.95.162" + subject="comment 4" + date="2014-05-19T16:28:01Z" + content=""" +I can reproduce this problem on OSX. + +I've only gotten as far as seeing that the gcrypt repository never gets initialized as a git repository. It has a config file, but no objects are ever pushed to it. This is why gcrypt sees no repository there in subsequent runs. + +This is a bug in gcrypt, so filed: +"""]]