From 387a76c51130f92585793bea2a1d24037397fb3e Mon Sep 17 00:00:00 2001 From: "http://alan.petitepomme.net/" Date: Fri, 14 Mar 2014 18:11:52 +0000 Subject: [PATCH] Added a comment --- ..._0c9a6c8a92d6c6e04ae3a8349b799c60._comment | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/forum/How_do_I_get_rid_of_a_wrong_remote_uuid__63__/comment_5_0c9a6c8a92d6c6e04ae3a8349b799c60._comment diff --git a/doc/forum/How_do_I_get_rid_of_a_wrong_remote_uuid__63__/comment_5_0c9a6c8a92d6c6e04ae3a8349b799c60._comment b/doc/forum/How_do_I_get_rid_of_a_wrong_remote_uuid__63__/comment_5_0c9a6c8a92d6c6e04ae3a8349b799c60._comment new file mode 100644 index 0000000000..9807fb7d9f --- /dev/null +++ b/doc/forum/How_do_I_get_rid_of_a_wrong_remote_uuid__63__/comment_5_0c9a6c8a92d6c6e04ae3a8349b799c60._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="http://alan.petitepomme.net/" + nickname="Alan Schmitt" + subject="comment 5" + date="2014-03-14T18:11:52Z" + content=""" +Thanks, it worked! + +Regarding how I got into that state, here is what happened: +- I configured a new repository (git init, git annex init) on machine B +- I added that repository as a remote from machine A +- I started pushing files from machine A to machine B, starting with the file that later showed this problem +- I then noticed that, although the files were said to be successfully sent, I could not see them on machine B (no symbolic link was created), even after a \"git annex sync\" there +- I decided to start over, deleting the annex, and creating it from a clone of an existing annex +- This resulted in a duplicated UUID for the same path, which led to this problem + +Maybe some documentation on how to cleanly start over when things get in a bad state would be very useful. + +Thanks again, + +Alan +"""]]