response

1 files changed, 29 insertions, 0 deletions

diff --git a/doc/bugs/Initial___34__Make_repository__34___fails_due_to___34__empty_ident_name___40__for___60__email-address__62____41___not_allowed__34__/comment_1_267b252368dca4803d706c70a3ef3244._comment b/doc/bugs/Initial___34__Make_repository__34___fails_due_to___34__empty_ident_name___40__for___60__email-address__62____41___not_allowed__34__/comment_1_267b252368dca4803d706c70a3ef3244._comment
new file mode 100644
index 000000000..376ea92ef
--- /dev/null
+++ b/doc/bugs/Initial___34__Make_repository__34___fails_due_to___34__empty_ident_name___40__for___60__email-address__62____41___not_allowed__34__/comment_1_267b252368dca4803d706c70a3ef3244._comment
@@ -0,0 +1,29 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-11-10T19:45:36Z"
+ content="""
+I was able to completely reproduce this in every particular, except for one
+important thing:
+
+The webapp *was* able to advance; the repository was created, and 
+when I looked inside its .git/config, I saw as expected:
+
+	[user]
+	name = foo
+	email = bar
+
+So, as far as I can see, git-annex's existing code to detect when the
+system is so badly configured that git commit doesn't work, and fix the git
+configuration of the repository well enough for git commit to proceed, is
+working. The git error just occurs when git-annex is doing that probing.
+
+And, in your transcript, it says "(recording state in git...)" so
+it seems to have gotten past that git error just fine as well.
+
+If the webapp didn't advance beyond creating the repository, what error
+message was displayed **in the webapp**?
+
+Currently, my guess is you saw scary stuff on the console and assumed it
+meant it wouldn't work, but it did.
+"""]]