respond to all of a user's bug reports at once.. they had copied a repo and so had duplicated annex.uuid

4 files changed, 30 insertions, 0 deletions

diff --git a/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn
index 7381cf7f3..82afb6135 100644
--- a/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn
+++ b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn
@@ -8,6 +8,9 @@ Meanwhile, those files also reside in a remote. git-annex-whereis does show ther
 
 Note that dropping files in current repo (``git annex drop``) and re-getting (``git annex get``) does download the files from that remote. However, a subsequent ``git annext whereis`` again shows 1 copy --- at that remote only.
 
+> Because you have 2 repositories with the same annex.uuid, which is not
+> allowed. Fix your misconfigured repo to not have the same annex.uuid and
+> that won't happen. [[done]] --[[Joey]]
 
 ### What steps will reproduce the problem?
 
diff --git a/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/.comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment.swp b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/.comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment.swp
new file mode 100644
index 000000000..88ae1a2cc
--- /dev/null
+++ b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/.comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment.swp
diff --git a/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment
new file mode 100644
index 000000000..344ecfe23
--- /dev/null
+++ b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-11-30T19:55:05Z"
+ content="""
+Well, you also filed the bug report  
+[[Unable_to_take_transfer_lock]], where you said something about having
+copied the repository over SMB using `cp` and some kind of OSX copy and
+paste.
+
+So, if you did that, it seems likely that you have 2 git repositories with
+the same annex.uuid setting. In fact this is confirmed by [another bug
+report](http://git-annex.branchable.com/bugs/remote_repo_marked_as___34__here__34__/)
+you filed.
+
+Since git-annex expects each repository to have a unique annex.uuid, this
+is going to confuse it badly. Don't do that. Use `git clone` to make a clone
+of a git repository.
+"""]]
diff --git a/doc/bugs/whereis_claims_file_is_not_here__44___but_it_is_available_both_here_and_in_another_remote/comment_4_b70e83a44a85b006c2c6105660cd6a7a._comment b/doc/bugs/whereis_claims_file_is_not_here__44___but_it_is_available_both_here_and_in_another_remote/comment_4_b70e83a44a85b006c2c6105660cd6a7a._comment
new file mode 100644
index 000000000..68e414e53
--- /dev/null
+++ b/doc/bugs/whereis_claims_file_is_not_here__44___but_it_is_available_both_here_and_in_another_remote/comment_4_b70e83a44a85b006c2c6105660cd6a7a._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2015-11-30T20:08:10Z"
+ content="""
+@jhannwong you had [2 repos with the same annex.uuid](http://git-annex.branchable.com/bugs/remote_repo_marked_as___34__here__34__)
+so if you had the same problem, it was a misconfiguration on your part.
+"""]]