diff options
-rw-r--r-- | doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_1_2a1c20b432dd839e0153827e151fbbc0._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_1_2a1c20b432dd839e0153827e151fbbc0._comment b/doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_1_2a1c20b432dd839e0153827e151fbbc0._comment new file mode 100644 index 000000000..82ccd0f5c --- /dev/null +++ b/doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_1_2a1c20b432dd839e0153827e151fbbc0._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-11-07T17:34:32Z" + content=""" +If you pass the --debug option, the debug output includes a transcript of +the S3 http session. + +I can confirm there have been no recent changes to git-annex's S3 support. +Of course it's possible that if you upgraded git-annex the version of +<http://hackage.haskell.org/package/aws> used changed, but that seems +unlikely to cause such breakage. + +Seems likely that if it's stopped working, something changed on Google's +end.. +"""]] |