Merge branch 'master' of ssh://git-annex.branchable.com

13 files changed, 143 insertions, 0 deletions

diff --git a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_2_53f2de3d3993821d8502fd08a0fcce12._comment b/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_2_53f2de3d3993821d8502fd08a0fcce12._comment
new file mode 100644
index 000000000..69d795865
--- /dev/null
+++ b/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_2_53f2de3d3993821d8502fd08a0fcce12._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 2"
+ date="2013-03-19T00:07:23Z"
+ content="""
+It seems to me that --bindir ~/bin will work, but --bindir=~/bin will not; it prevents the shell's tilde expansion from working. 
+"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_258a376cff4c62bc4be919322bb1bd88._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_258a376cff4c62bc4be919322bb1bd88._comment
new file mode 100644
index 000000000..5150d9611
--- /dev/null
+++ b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_258a376cff4c62bc4be919322bb1bd88._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 10"
+ date="2013-03-19T00:14:59Z"
+ content="""
+Comment 7 was misplaced. Apologies.
+
+Hint for stracing: If you strace \"git-annex\" instead of \"git annex\", you don't need to strace -f, which keeps it a lot simpler.
+"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_5_80444a509cc340f5eb3cd08b193fd389._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_5_80444a509cc340f5eb3cd08b193fd389._comment
new file mode 100644
index 000000000..ecc4a93e1
--- /dev/null
+++ b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_5_80444a509cc340f5eb3cd08b193fd389._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 5"
+ date="2013-03-18T17:23:56Z"
+ content="""
+Does this only happen with one file, or with all files?
+
+I think you will need to strace git-annex to determine what the problem is. I cannot see how this could happen in indirect mode.
+"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_6_4c6b99cd67b4aa742da5101fb1b379f7._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_6_4c6b99cd67b4aa742da5101fb1b379f7._comment
new file mode 100644
index 000000000..977eed926
--- /dev/null
+++ b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_6_4c6b99cd67b4aa742da5101fb1b379f7._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
+ nickname="John"
+ subject="comment 6"
+ date="2013-03-18T18:42:14Z"
+ content="""
+It only happens with this one file, because it's the last file to be copied to the remote repository.
+"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_7_131a1b65c8008cf9f02c93d4fb75720b._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_7_131a1b65c8008cf9f02c93d4fb75720b._comment
new file mode 100644
index 000000000..515976b85
--- /dev/null
+++ b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_7_131a1b65c8008cf9f02c93d4fb75720b._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 7"
+ date="2013-03-18T23:05:26Z"
+ content="""
+The standalone linux tarball will work on 64 or 32 bit systems, as long as they are capable of linking 32 bit elf executables. I cannot test if Arch Linux is incapable of this.
+
+I'm getting a bit tired of wild tangents, can we you just find someplace, be it a Debian chroot or whatever, to run the standalone linux tarball and test if DAV works there?
+"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_8_f45cdd2b6acc5f458b67539fced0e529._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_8_f45cdd2b6acc5f458b67539fced0e529._comment
new file mode 100644
index 000000000..59014a082
--- /dev/null
+++ b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_8_f45cdd2b6acc5f458b67539fced0e529._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 8"
+ date="2013-03-18T23:08:06Z"
+ content="""
+I don't understand what you're saying about it being the last file to be copied. This can't be stopping the copy from processing files after the one it fails on, and the order of the file in the list of files it's processing cannot be significant, unless you know something I don't know.
+
+What I meant to ask you is whether there is one, particular, specific file on your system that it refuses to copy, or whether it refuses to copy all files, or what.
+
+Anyway, you are going to need to send me a strace, I'm utterly stuck on this.
+"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_9_5a455dd14fb9d3ff408bb3f81e366c38._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_9_5a455dd14fb9d3ff408bb3f81e366c38._comment
new file mode 100644
index 000000000..145458120
--- /dev/null
+++ b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_9_5a455dd14fb9d3ff408bb3f81e366c38._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
+ nickname="John"
+ subject="comment 9"
+ date="2013-03-18T23:46:39Z"
+ content="""
+I don't quite follow what comment 7 is trying to say, did you intend that to go to another bug report?
+
+As for strace, I'll give it a try tomorrow.
+"""]]
diff --git a/doc/bugs/Crash_when_adding_jabber_account_/comment_3_e59f8813bf1a7c4e3c8c120fe82348b9._comment b/doc/bugs/Crash_when_adding_jabber_account_/comment_3_e59f8813bf1a7c4e3c8c120fe82348b9._comment
new file mode 100644
index 000000000..763f6fe53
--- /dev/null
+++ b/doc/bugs/Crash_when_adding_jabber_account_/comment_3_e59f8813bf1a7c4e3c8c120fe82348b9._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 3"
+ date="2013-03-18T23:42:55Z"
+ content="""
+I tried to reproduce this with the standalone i386 tarball for 4.20130314. Was able to add a jabber account using my google talk account with no crash.
+
+Given the age of this bug report, I'm just going to close it. But if you still see it with the current verison, please let me know! (And I guess you'd have to tell me which jabber server you're using then..)
+"""]]
diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_2_f2c1aa84a0d04e840cb34ae15eb1cb03._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_2_f2c1aa84a0d04e840cb34ae15eb1cb03._comment
new file mode 100644
index 000000000..937e9cf8e
--- /dev/null
+++ b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_2_f2c1aa84a0d04e840cb34ae15eb1cb03._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 2"
+ date="2013-03-18T23:25:24Z"
+ content="""
+This is an important bug. Could you please get back to me so I can debug it?
+"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_14_e1da141eefb0445c217e5f5c119356da._comment b/doc/bugs/WEBDAV_443/comment_14_e1da141eefb0445c217e5f5c119356da._comment
new file mode 100644
index 000000000..5097df183
--- /dev/null
+++ b/doc/bugs/WEBDAV_443/comment_14_e1da141eefb0445c217e5f5c119356da._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 14"
+ date="2013-03-18T16:54:02Z"
+ content="""
+Given that line 69 of runshell is a newline, and that runshell does not ever try to run git-annex-shell, I wonder what you downloaded exactly...
+"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_15_41c3134bcc222b97bf183559723713d9._comment b/doc/bugs/WEBDAV_443/comment_15_41c3134bcc222b97bf183559723713d9._comment
new file mode 100644
index 000000000..5bf5bafe4
--- /dev/null
+++ b/doc/bugs/WEBDAV_443/comment_15_41c3134bcc222b97bf183559723713d9._comment
@@ -0,0 +1,27 @@
+[[!comment format=mdwn
+ username="https://pradermecker.myopenid.com/"
+ ip="195.244.162.7"
+ subject="comment 15"
+ date="2013-03-18T19:07:31Z"
+ content="""
+Euh. I actually feel stupid enough with this but ...
+
+I have try first with your link and it gives me:
+
+```
+./runshell: line 75: /home/vagrant/programs/git-annex.linux/bin/sh: No such file or directory
+```
+
+As I told you I then try the AUR package : https://aur.archlinux.org/packages/git-annex-standalone/
+
+And it does give me the same error on line 69.
+
+It is the same line (3 lines before the end):
+
+```
+exec \"$cmd\" \"$@\"
+```
+
+I really don't get it because the file is there ... and the first sanity checks of the script have pass.
+
+"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_16_89621b526065b5bef753ce75db1af7b5._comment b/doc/bugs/WEBDAV_443/comment_16_89621b526065b5bef753ce75db1af7b5._comment
new file mode 100644
index 000000000..059a8ee00
--- /dev/null
+++ b/doc/bugs/WEBDAV_443/comment_16_89621b526065b5bef753ce75db1af7b5._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="https://pradermecker.myopenid.com/"
+ ip="195.244.162.7"
+ subject="comment 16"
+ date="2013-03-18T19:31:42Z"
+ content="""
+Actually it is even worse ...
+
+With your link, line 75 is actually 2 lines below (sh).
+
+So same command (runshell), same error, different places (I guess it is always the last line executed) ...
+
+Is it supposed to work fine in 64 bits also ?
+"""]]
diff --git a/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_3_7d81ea83966821b1dbbc4c7d161e09bd._comment b/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_3_7d81ea83966821b1dbbc4c7d161e09bd._comment
new file mode 100644
index 000000000..83997a2f4
--- /dev/null
+++ b/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_3_7d81ea83966821b1dbbc4c7d161e09bd._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 3"
+ date="2013-03-18T23:28:10Z"
+ content="""
+It's been a month, any news on this bug?
+"""]]