1 files changed, 44 insertions, 0 deletions

diff --git a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn b/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn
new file mode 100644
index 000000000..8ec02de84
--- /dev/null
+++ b/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn
@@ -0,0 +1,44 @@
+### Please describe the problem.
+
+Creating two repos with the same name causes git annex dead to randomly choose one. This is reasonable except that it can choose to mark an already dead remote dead (as long as it shares the name), causing it to actually do nothing.
+
+I think preferring to mark live repos dead and printing a warning when multiple repos could have been chosen would be a good solution.
+
+### What steps will reproduce the problem?
+
+1. Create a new repo /somecopy
+
+    git clone /central /somecopy
+    cd /somecopy
+    git annex init somecopy
+    git annex sync
+    cd /
+
+Now, git annex status shows somecopy as an existing repo.
+
+2. Destroy the new repo
+
+    rm -rf /somecopy
+    cd /central
+    git annex dead somecopy
+
+git annex status correctly hides somecopy, and it is properly dead.
+
+3. create it again with the same name, but new UUID
+
+    git clone /central /somecopy
+    cd /somecopy
+    git annex init somecopy
+    git annex sync
+    cd /
+
+4. Destroy the second repo
+
+    rm -rf /somecopy
+    cd /central
+
+Now, git annex dead somecopy will randomly (based on the order of the UUIDs?) choose to mark dead the already dead old repo or the new repo, in both cases showing success to the user.
+
+### What version of git-annex are you using? On what operating system?
+
+git-annex 4.20131024 on linux. Also occurs on OSX.