diff options
| -rw-r--r-- | doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_4_64338d2d77dcbabd16b55eb145f40dc6._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_4_64338d2d77dcbabd16b55eb145f40dc6._comment b/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_4_64338d2d77dcbabd16b55eb145f40dc6._comment new file mode 100644 index 000000000..d4a05ce8e --- /dev/null +++ b/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_4_64338d2d77dcbabd16b55eb145f40dc6._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkZktNHFhxC1kYA9KKdKpYJO4clq9WDsjE" + nickname="Jason" + subject="comment 4" + date="2013-04-25T01:18:00Z" + content=""" +Oh! That might be it! During the whole \"I have two remotes with the name s3\" situation, it seems that both of them in my .git/config ended up with the same uuid, even though the original one had a different uuid. If I change it back, I end up getting an access denied when I try to `git annex get ...`. Progress! + +I thought that you were supposed to do a `git annex initremote s3` from a clone to enable a remote with the credentials stored in the repo. It seems that internally something still thinks that the \"s3\" remote has the new uuid. When I run that command it changes the uuid back to the new (invalid) one. + +Is there a way I can totally remove the bad s3 (which I've partially renamed to s3thefirst) remote from my history/repo (I'm pretty sure it's been synced back up to origin at this point) or properly rename it so it doesn't keep getting confused? Hopefully that will address my problem. +"""]] |