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

14 files changed, 127 insertions, 0 deletions

diff --git a/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_3_67bfccf0934075559d439b1deafc001e._comment b/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_3_67bfccf0934075559d439b1deafc001e._comment
new file mode 100644
index 000000000..edf7c781b
--- /dev/null
+++ b/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_3_67bfccf0934075559d439b1deafc001e._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnX1msQxnLoSeu7q-i-c9BWghonsN7Qmns"
+ nickname="Jan Ulrich"
+ subject="comment 3"
+ date="2014-03-05T11:47:06Z"
+ content="""
+I observe something similar. Today git-annex started to repair a repository. CPU is at 100%, I can still work because I have a multikernel system, so I'll wait and see if it comes to an end.
+
+"""]]
diff --git a/doc/bugs/Box.com_ReposnseTimeout/comment_3_b73450b3a9728ac6f34f0e63255f6fa9._comment b/doc/bugs/Box.com_ReposnseTimeout/comment_3_b73450b3a9728ac6f34f0e63255f6fa9._comment
new file mode 100644
index 000000000..e6585b6a2
--- /dev/null
+++ b/doc/bugs/Box.com_ReposnseTimeout/comment_3_b73450b3a9728ac6f34f0e63255f6fa9._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8"
+ nickname="Jon Ander"
+ subject="comment 3"
+ date="2014-03-05T08:10:25Z"
+ content="""
+My connection is pretty fast, I've just copied a 77MB folder through Box's webdav with my file manager in ~90sec and I have never seen a timeout when using my file manager, all uploads finish properly.
+"""]]
diff --git a/doc/bugs/Box.com_ReposnseTimeout/comment_4_0bd9eb5947a21d0657e79cf276923bb5._comment b/doc/bugs/Box.com_ReposnseTimeout/comment_4_0bd9eb5947a21d0657e79cf276923bb5._comment
new file mode 100644
index 000000000..c95d3ceb4
--- /dev/null
+++ b/doc/bugs/Box.com_ReposnseTimeout/comment_4_0bd9eb5947a21d0657e79cf276923bb5._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.146"
+ subject="comment 4"
+ date="2014-03-05T17:11:40Z"
+ content="""
+Previous bug report about this with much more information, please do any followup there:
+[[bugs/box.com_never_stops_syncing.]]
+"""]]
diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_5_792ab128a91c66e4ddeaa69d09430a78._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_5_792ab128a91c66e4ddeaa69d09430a78._comment
new file mode 100644
index 000000000..d5e56151d
--- /dev/null
+++ b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_5_792ab128a91c66e4ddeaa69d09430a78._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="http://grossmeier.net/"
+ nickname="greg"
+ subject="comment 5"
+ date="2014-03-05T04:34:49Z"
+ content="""
+Still seeing it with version 5.20140227
+
+git-annex unused shows 110 keys.
+
+git-annex copy --unused --to $anyremote just returns very quickly without doing anything.
+
+git-annex copy --all --to $anyremote does go through every key and checks.
+
+git-annex copy --key=$some_key_listed_in_unused --to $anyremote also just returns quickly without checking.
+
+I even untrusted the repository via vicfg and passing the --untrust=remote argument.
+
+Again, a direct mode repo that is also assistant'd.
+"""]]
diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_6_e44a16ef3358a6fbcc6ed6b3a31f3273._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_6_e44a16ef3358a6fbcc6ed6b3a31f3273._comment
new file mode 100644
index 000000000..eae21f79d
--- /dev/null
+++ b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_6_e44a16ef3358a6fbcc6ed6b3a31f3273._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://grossmeier.net/"
+ nickname="greg"
+ subject="comment 6"
+ date="2014-03-05T04:38:26Z"
+ content="""
+Also, in another non-direct/non-assistant'd repo, things work as expected.
+"""]]
diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_7_635acd64b524c682c58f26ae96ae0d7d._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_7_635acd64b524c682c58f26ae96ae0d7d._comment
new file mode 100644
index 000000000..52cfc575c
--- /dev/null
+++ b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_7_635acd64b524c682c58f26ae96ae0d7d._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.146"
+ subject="comment 7"
+ date="2014-03-05T17:08:19Z"
+ content="""
+The only reason copy --key would do nothing is if the key is not locally present in your repository.
+
+Please check if the keys listed by `git annex unused` are present in `.git/annex/objects/`
+"""]]
diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment
new file mode 100644
index 000000000..0f20d9164
--- /dev/null
+++ b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.146"
+ subject="comment 3"
+ date="2014-03-05T16:56:14Z"
+ content="""
+Older versions of git-annex did not preserve more than the very end of the extension when using SHA*E backends, so I guess you added the respective files using two different versions.
+"""]]
diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_4_deb848e50f6767d8a5f4348137744ec2._comment b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_4_deb848e50f6767d8a5f4348137744ec2._comment
new file mode 100644
index 000000000..e53e5c2dd
--- /dev/null
+++ b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_4_deb848e50f6767d8a5f4348137744ec2._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawlmOvQXLmGkQAUOIkPBQtsd9d45NqcX80M"
+ nickname="Jan"
+ subject="comment 4"
+ date="2014-03-05T17:07:05Z"
+ content="""
+Ah, so it's a matter of `.JPG.cam` vs `.cam` as an extension -- that makes sense, I do use different versions on these two remotes. Is there some easy way of getting them back to a single underlying content apart from doing that by hand?
+"""]]
diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment
new file mode 100644
index 000000000..c50d75476
--- /dev/null
+++ b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.146"
+ subject="comment 5"
+ date="2014-03-05T18:02:08Z"
+ content="""
+Well, the easy way, assuming that you don't need the extension in the key at all, is to run `git annex migrate --backend=SHA512 *.cam` in both repositories.
+
+You can also play tricks with `git annex rekey`. I don't know if I'd recommend doing so.
+"""]]
diff --git a/doc/forum/Auto_sync_with_music_player.mdwn b/doc/forum/Auto_sync_with_music_player.mdwn
new file mode 100644
index 000000000..e4a5543b4
--- /dev/null
+++ b/doc/forum/Auto_sync_with_music_player.mdwn
@@ -0,0 +1 @@
+I have a music directory under Nexus 5 which is a git-annex repository. If I sync the same with remote repository, newly added songs or modified songs(modifed id3 tags) will not sync with music player. But if I use Android File Transfer to transfer songs, it will sync music player. The songs which are transferred using git-annex will reflect in music player only after restart. Do we have to execute any command which will sync music player.
diff --git a/doc/forum/Too_big_to_fsck/comment_5_2b5406768fff2834f7aefa76ef949de2._comment b/doc/forum/Too_big_to_fsck/comment_5_2b5406768fff2834f7aefa76ef949de2._comment
new file mode 100644
index 000000000..923e1ccba
--- /dev/null
+++ b/doc/forum/Too_big_to_fsck/comment_5_2b5406768fff2834f7aefa76ef949de2._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.146"
+ subject="comment 5"
+ date="2014-03-05T16:53:33Z"
+ content="""
+You have an older version of git, which does not support --no-dangling.
+
+git-annex will detect that, and omit the option. This does make it more likely that git fsck is outputing a ton of information, so I continue to think that's the most likely cause of the memory use.
+
+Please verify with: git fsck --no-reflogs |wc
+"""]]
diff --git a/doc/forum/WARNING:_linker:git-annex_has_text_relocations....mdwn b/doc/forum/WARNING:_linker:git-annex_has_text_relocations....mdwn
new file mode 100644
index 000000000..2d9ee1324
--- /dev/null
+++ b/doc/forum/WARNING:_linker:git-annex_has_text_relocations....mdwn
@@ -0,0 +1,7 @@
+I have configured git-annex on my Nexus 5. Even though it works fantastic, it shows some warning messages.
+
+1: 'git-annex sync' :  WARNING: linker: git-annex has text relocations. This is wasting memory and is a security risk. Please fix.
+
+2: 'git log': error: cannot run less. No such file or directory.
+
+Both the commands will work has expected with these warnings. What could be the issue here.
diff --git a/doc/forum/copy_fails_for_some_fails_without_explanation.mdwn b/doc/forum/copy_fails_for_some_fails_without_explanation.mdwn
new file mode 100644
index 000000000..d4bcbf08c
--- /dev/null
+++ b/doc/forum/copy_fails_for_some_fails_without_explanation.mdwn
@@ -0,0 +1,5 @@
+I have a large direct-mode repository whose files I'm trying to copy to a non-direct-mode repository.  Both repositories live on an HDD attached to an rpi.
+
+When I do $ git annex copy --to pi dirs/to/copy, the copy starts out OK, but eventually many files fail to copy.  The only diagnostic I get is "failed".  Judging from the backscroll, I don't see a strong pattern to the files which fail to copy; they're kind of interspersed amongst files which were successfully copied.  If I try to copy one of these failed files explicitly (git annex copy --to pi file/which/failed), this succeeds.  I have plenty of free space on the disk.
+
+Is there a way to get more diagnostics out of git annex so I can see why these files are failing to copy?
diff --git a/doc/forum/copy_fails_for_some_fails_without_explanation/comment_1_e456604b26ed9c72b0a88cfb57f1a475._comment b/doc/forum/copy_fails_for_some_fails_without_explanation/comment_1_e456604b26ed9c72b0a88cfb57f1a475._comment
new file mode 100644
index 000000000..dba07bfd5
--- /dev/null
+++ b/doc/forum/copy_fails_for_some_fails_without_explanation/comment_1_e456604b26ed9c72b0a88cfb57f1a475._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c"
+ nickname="Justin"
+ subject="comment 1"
+ date="2014-03-05T16:11:27Z"
+ content="""
+I tried git annex sync --content, and it failed to copy some files with
+
+  git: createProcess: resource exhausted (Resource temporarily unavailable)
+
+So this sounds like fork is failing; I'm probably exhausting my poor pi's RAM.  Maybe the same thing is happening for git annex copy.  I'll run strace to see.
+"""]]