mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
http://joeyh.name/ 2013-04-25 02:14:18 +00:00 • committed by admin
parent 49547ad32d
commit 349212bd7f
1 changed files with 16 additions and 0 deletions

16
doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_5_dd66c9ea0c83388f6826751944330d10._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 5"
date="2013-04-25T02:14:18Z"
content="""
Yes, when you run `git annex initremote $remotename` with no other parameters, it enables a remote from the stored configuration.
Which does not include `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID`; you need to set those and then
you should not get access denied.
You seem to say your .git/config contains two remotes with the same name, but I don't think that's possible.
I don't know how you could end up with two remotes with the same name in `git show git-annex:remote.log`, unless the two were added in separate repositories which were then synced together. Since this is not a usual situation there's not any UI to deal with it. I've just committed a change that will make `initremote` prefer remotes that have not been marked dead when there's a naming comflict.
However, I'm more curious how this situation came about. I have not been able to reproduce the problem when enabling a S3 remote using the webapp.
"""]]