From: Joey Hess Date: Wed, 2 Dec 2015 17:20:15 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~322^2~33 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=dae7162856b782e3f992a7807f5a827fed086d95;p=git-annex.git comment --- diff --git a/doc/bugs/regression_with_S3_creds_not_used/comment_1_df5416ee63c8f026f3b3c77c74b67ce4._comment b/doc/bugs/regression_with_S3_creds_not_used/comment_1_df5416ee63c8f026f3b3c77c74b67ce4._comment new file mode 100644 index 0000000000..dbfb7c0db1 --- /dev/null +++ b/doc/bugs/regression_with_S3_creds_not_used/comment_1_df5416ee63c8f026f3b3c77c74b67ce4._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-12-02T17:11:47Z" + content=""" +I tried reproducing this with the current version of git-annex on windows, +and didn't see the problem. The creds file was used when the AWS_* +environment variables were not set. + +What was the version of git-annex that was working before this reversion? + +Does the creds files corresponding to the uuid of your S3 remote exist? +Does it contain 2 lines, for the access key and secret key, respectively? + +The webapp failure message seems to indicate that git-annex is has found +creds, but they somehow have the wrong values. Does the s3ErrorAccessKeyId +that you redacted match the access key that you told git-annex to use? +(Note that it should be ok to show the s3 access key as long as you don't +also show what the secret key is AFAIK.) +"""]]