From b6cfb9a73adcd14bf653e65e0314423a0d3bc346 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 13 Feb 2017 14:53:55 -0400 Subject: [PATCH] comment --- ...t_1_ed0ead0b09ddbe52d42150a281d84f5c._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Use_existing_S3_bucket/comment_1_ed0ead0b09ddbe52d42150a281d84f5c._comment diff --git a/doc/forum/Use_existing_S3_bucket/comment_1_ed0ead0b09ddbe52d42150a281d84f5c._comment b/doc/forum/Use_existing_S3_bucket/comment_1_ed0ead0b09ddbe52d42150a281d84f5c._comment new file mode 100644 index 0000000000..87c4c1345c --- /dev/null +++ b/doc/forum/Use_existing_S3_bucket/comment_1_ed0ead0b09ddbe52d42150a281d84f5c._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-02-13T18:01:40Z" + content=""" +It's not supposed to fail when the bucket already exists. There is an +explicit check to see whether the bucket exists in current versions. + +Unfortunately, git-annex can't support the Frankfurt datacenter, +until this API problem gets fixed + +In my tests, it doesn't fail that way when the bucket already exists. +I didn't create the bucket in Frankfurt though, and it could be +that due to the API problem it fails to notice that the bucket in Frankfurt +already exists. +"""]]