From b0dc1b98c37b955b79b83cd724b0f3ec16b45a59 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 27 Mar 2013 16:18:15 +0000 Subject: [PATCH 1/4] Added a comment --- ...mment_1_f708d87aa65cd38c20087859d3ab2dc7._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_1_f708d87aa65cd38c20087859d3ab2dc7._comment diff --git a/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_1_f708d87aa65cd38c20087859d3ab2dc7._comment b/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_1_f708d87aa65cd38c20087859d3ab2dc7._comment new file mode 100644 index 0000000000..458e31327d --- /dev/null +++ b/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_1_f708d87aa65cd38c20087859d3ab2dc7._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 1" + date="2013-03-27T16:18:14Z" + content=""" +What is this GITWRAP? That is not part of git-annex, I suspect it's a locally set up wrapper around git of some sort. + +--debug causes the assistant to log to `.git/annex/daemon.log`, there may be useful information in there. In particular it's not at all clear whether the web browser is segfaulting, or whether the crash occurs before the web browser is started. + +Does your SE linux policy allow git-annex to run your web browser? What happens if you start the assistant and then manually open file:///home/zerodogg/Documents/annexed/.git/annex/webapp.html in your web browser? +"""]] From 03202c945d7001ecfd5ca9717ac4db1f0dfaaa67 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 27 Mar 2013 16:38:10 +0000 Subject: [PATCH 2/4] Added a comment --- .../comment_4_b31496b37046a9886f632ba4f11c56e3._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_4_b31496b37046a9886f632ba4f11c56e3._comment diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_4_b31496b37046a9886f632ba4f11c56e3._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_4_b31496b37046a9886f632ba4f11c56e3._comment new file mode 100644 index 0000000000..272d2a7591 --- /dev/null +++ b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_4_b31496b37046a9886f632ba4f11c56e3._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 4" + date="2013-03-27T16:38:07Z" + content=""" +@Xyem, sounds like an unrelated bug. Also, no git-annex commands run `git status`. You can find other git commands that may be using a lot of memory by passing the --debug flag to git-annex. +"""]] From c5a64b880049a19453429f90ca403d09fab80cd9 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 27 Mar 2013 16:38:47 +0000 Subject: [PATCH 3/4] Added a comment --- .../comment_8_2627b41f80c7511b27464e2040b128a8._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/special_remotes/webdav/comment_8_2627b41f80c7511b27464e2040b128a8._comment diff --git a/doc/special_remotes/webdav/comment_8_2627b41f80c7511b27464e2040b128a8._comment b/doc/special_remotes/webdav/comment_8_2627b41f80c7511b27464e2040b128a8._comment new file mode 100644 index 0000000000..96ae19d111 --- /dev/null +++ b/doc/special_remotes/webdav/comment_8_2627b41f80c7511b27464e2040b128a8._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 8" + date="2013-03-27T16:38:47Z" + content=""" +I don't think the checking of SSL certificates can currently be disabled. +"""]] From 894e6863abcfc8b36efb853cce0bdf32a91ce7a2 Mon Sep 17 00:00:00 2001 From: Xyem Date: Wed, 27 Mar 2013 16:50:58 +0000 Subject: [PATCH 4/4] Added a comment --- ...mment_5_d25ff424dda1f6021c1ba20f79d71ffc._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_5_d25ff424dda1f6021c1ba20f79d71ffc._comment diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_5_d25ff424dda1f6021c1ba20f79d71ffc._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_5_d25ff424dda1f6021c1ba20f79d71ffc._comment new file mode 100644 index 0000000000..958eb77337 --- /dev/null +++ b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_5_d25ff424dda1f6021c1ba20f79d71ffc._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="Xyem" + ip="87.194.19.134" + subject="comment 5" + date="2013-03-27T16:50:58Z" + content=""" +@joey: Hm.. I'm sure it was 'git annex sync' that initially consumed all RAM by spawning a lot of 'git status' processes. However, I can't replicate it anymore as I found a way to make the repository useable again. + +I went low into the directory structure and added/committed from there. Now I can 'git annex sync' and 'git status' from the annex root without any problems. + +Sorry for cluttering this bug report up, thought it might be related/of some help. +"""]]