From 3c2a0efb42a0a44d1e7ccd72a10843a823505b60 Mon Sep 17 00:00:00 2001 From: "http://alan.petitepomme.net/" Date: Fri, 7 Mar 2014 18:03:47 +0000 Subject: Added a comment: still need to remove the remote after a "dead" --- .../comment_7_4e6baa41bfee6edf2b17d4ade2909c7b._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/tips/what_to_do_when_you_lose_a_repository/comment_7_4e6baa41bfee6edf2b17d4ade2909c7b._comment diff --git a/doc/tips/what_to_do_when_you_lose_a_repository/comment_7_4e6baa41bfee6edf2b17d4ade2909c7b._comment b/doc/tips/what_to_do_when_you_lose_a_repository/comment_7_4e6baa41bfee6edf2b17d4ade2909c7b._comment new file mode 100644 index 000000000..3b4b79da3 --- /dev/null +++ b/doc/tips/what_to_do_when_you_lose_a_repository/comment_7_4e6baa41bfee6edf2b17d4ade2909c7b._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="http://alan.petitepomme.net/" + nickname="Alan Schmitt" + subject="still need to remove the remote after a "dead"" + date="2014-03-07T18:03:47Z" + content=""" +Hello, + +I decommissioned a machine and installed git annex on another machine, with the same IP as the initial one. To avoid errors, I declared the first repository as dead and created a new one (with a new remote). However, I also had to remove the git remote to the dead machine as \"git annex sync\" kept telling me synchronizing to this dead machine failed (the ssh succeeded, using the name automatically generated by git annex, but the repository was not at the same path on the new machine, so it could not find it). + +Should a dead repository not tried to be synchronized at all during git annex sync? + +Thanks, + +Alan +"""]] -- cgit v1.2.3 From 196e31220e76fd84d402bfa3b6cd4d78e74adf7d Mon Sep 17 00:00:00 2001 From: "http://alan.petitepomme.net/" Date: Fri, 7 Mar 2014 19:11:56 +0000 Subject: --- .../How_do_I_get_rid_of_a_wrong_remote_uuid__63__.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/How_do_I_get_rid_of_a_wrong_remote_uuid__63__.mdwn diff --git a/doc/forum/How_do_I_get_rid_of_a_wrong_remote_uuid__63__.mdwn b/doc/forum/How_do_I_get_rid_of_a_wrong_remote_uuid__63__.mdwn new file mode 100644 index 000000000..209e0f6a7 --- /dev/null +++ b/doc/forum/How_do_I_get_rid_of_a_wrong_remote_uuid__63__.mdwn @@ -0,0 +1,16 @@ +Hello, + +I had some trouble adding a remote (the files would not appear when I was copying them to the remote), so I started over and cloned an existing repository. + +Of course, as I started over, I had a duplicate uuid for the remote, which would cause problems when trying to copy (I would have an error "git-annex-shell: expected repository UUID 70582c7b-0b57-4087-a9d1-77b5f5f3c75e but found UUID 335699ea-d5b8-49ff-b207-1571b5969afe"). + +I finally managed to find the wrong uuid in the .git/config file (there was a duplicated entry for the remote) and I'm now able to copy things to the remote repository, and "git annex sync" works well. However I still see a mention of this repository when I do a "git annex whereis": + + cody:games schmitta$ git annex whereis + whereis dungeon_keeper_1.1.0.11.dmg (3 copies) + 1cdfb490-0660-41fb-b7ce-74b89abb9aac -- top + 335699ea-d5b8-49ff-b207-1571b5969afe -- here (cody) + 70582c7b-0b57-4087-a9d1-77b5f5f3c75e + + +Where can I find where this last line come from, and how can I get rid of it? I tried saying that this uuid is dead, but git annex tells me it's not a remote name. -- cgit v1.2.3