move conversation to a real bug report

9 files changed, 0 insertions, 104 deletions

diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_1_6a41bf7e2db83db3a01722b516fb6886._comment b/doc/walkthrough/recover_data_from_lost+found/comment_1_6a41bf7e2db83db3a01722b516fb6886._comment
deleted file mode 100644
index 59c30de53..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_1_6a41bf7e2db83db3a01722b516fb6886._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-05-12T00:07:29Z"
- content="""
-I followed this to re-inject files which git annex fsck listed as missing.
-
-For everyone of those files, I get 
-
-    git-annex-shell: key is already present in annex
-    rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-    rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.8]
-
-when trying to copy the files to the remote.
-
--- Richard
-"""]]
diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_2_9f5f1dbffb2dd24f4fcf8c2027bf0384._comment b/doc/walkthrough/recover_data_from_lost+found/comment_2_9f5f1dbffb2dd24f4fcf8c2027bf0384._comment
deleted file mode 100644
index 44aab3baa..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_2_9f5f1dbffb2dd24f4fcf8c2027bf0384._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-05-12T01:01:34Z"
- content="""
-Sounds like you probably didn't commit after the fsck, or didn't push so the other repository did not know the first had the content again -- but I'm not 100% sure.
-"""]]
diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_3_b596b5cfd3377e58dbbb5d509d026b90._comment b/doc/walkthrough/recover_data_from_lost+found/comment_3_b596b5cfd3377e58dbbb5d509d026b90._comment
deleted file mode 100644
index 4744db995..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_3_b596b5cfd3377e58dbbb5d509d026b90._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 3"
- date="2011-05-14T09:06:54Z"
- content="""
-As my comment from work is stuck in moderation:
-
-I ran this twice:
-
-    git pull && git annex add . && git annex copy . --to <remote> --fast --quiet && git commit -a -m \"$HOST $(date +%F--%H-%M-%S-%Z)\" && git push
-
-but nothing changed
-"""]]
diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_4_d7112c315fb016a8a399e24e9b6461d8._comment b/doc/walkthrough/recover_data_from_lost+found/comment_4_d7112c315fb016a8a399e24e9b6461d8._comment
deleted file mode 100644
index 1fb19ab19..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_4_d7112c315fb016a8a399e24e9b6461d8._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 4"
- date="2011-05-14T16:13:58Z"
- content="""
-Hmm. Old versions may have forgotten to git add a .git-annex location log file when recovering content with fsck. That could be another reason things are out of sync.
-
-But I'm not clear on which repo is trying to copy files to which.
-
-(NB: If the files were recovered on a bare git repo, fsck cannot update the location log there, which could also explain this.)
-"""]]
diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_5_4ea29a6f8152eddf806c536de33ef162._comment b/doc/walkthrough/recover_data_from_lost+found/comment_5_4ea29a6f8152eddf806c536de33ef162._comment
deleted file mode 100644
index 0a546bd88..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_5_4ea29a6f8152eddf806c536de33ef162._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 5"
- date="2011-05-14T19:03:43Z"
- content="""
-Version: 0.20110503
-
-My local non-bare repo is copying to a remote bare repo.
-
-I have been recovering in a non-bare repo.
-
-If there is anything I can send you to help... If I removed said files and went through http://git-annex.branchable.com/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/ -- would that help?
-"""]]
diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_6_0d85f114a103bd6532a3b3b24466012e._comment b/doc/walkthrough/recover_data_from_lost+found/comment_6_0d85f114a103bd6532a3b3b24466012e._comment
deleted file mode 100644
index 1e3f32531..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_6_0d85f114a103bd6532a3b3b24466012e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 6"
- date="2011-05-14T19:23:45Z"
- content="""
-Well, focus on a specific file that exhibits the problem. What does `git annex whereis` say about it? Is the content actually present in annex/objects/ on the bare repository? Does that contradict whereis?
-"""]]
diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_7_d38d5bee6d360b0ea852f39e3a7b1bc6._comment b/doc/walkthrough/recover_data_from_lost+found/comment_7_d38d5bee6d360b0ea852f39e3a7b1bc6._comment
deleted file mode 100644
index f7dfad68c..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_7_d38d5bee6d360b0ea852f39e3a7b1bc6._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 7"
- date="2011-05-14T23:13:15Z"
- content="""
-It exists locally, whereis tells me it exists locally and locally, only.
-
-The object is _not_ in the bare repo.
-
-The file _might_ have gone missing before I upgraded my annex backend version to 2. Could this be a factor?
-"""]]
diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_8_29c3de4bf5fbd990b230c443c0303cbe._comment b/doc/walkthrough/recover_data_from_lost+found/comment_8_29c3de4bf5fbd990b230c443c0303cbe._comment
deleted file mode 100644
index 01248914c..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_8_29c3de4bf5fbd990b230c443c0303cbe._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 8"
- date="2011-05-15T00:09:34Z"
- content="""
-What you're describing should be impossible; the error message shown can only occur if the object is present in the annex where `git-annex-shell recvkey` is run. So something strange is going on.
-
-Try reproducing it by running on the remote system, `git-annex-shell recvkey /remote/repo.git $key` .. if you can reproduce it, I guess the next thing to do will be to strace the command and see why it's thinking the object is there.
-"""]]
diff --git a/doc/walkthrough/recover_data_from_lost+found/comment_9_2cee4f6bd6db7518fd61453c595162c6._comment b/doc/walkthrough/recover_data_from_lost+found/comment_9_2cee4f6bd6db7518fd61453c595162c6._comment
deleted file mode 100644
index 2755cf331..000000000
--- a/doc/walkthrough/recover_data_from_lost+found/comment_9_2cee4f6bd6db7518fd61453c595162c6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 9"
- date="2011-05-15T09:16:49Z"
- content="""
-Just to make sure: How do I get $key? What I did was look at the path in the object store of the local repo and see if that exact same path & file existed in the remote.
-"""]]