From 0ab38a664f0f926aea9406df18188f56ce8b407c Mon Sep 17 00:00:00 2001 From: "wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d" Date: Sat, 12 Dec 2015 05:28:51 +0000 Subject: Added a comment --- .../comment_5_ebb7cc0e1c125765611014049d403d61._comment | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/bugs/STANDARD__95__IA_for_S3_remote_not_working/comment_5_ebb7cc0e1c125765611014049d403d61._comment diff --git a/doc/bugs/STANDARD__95__IA_for_S3_remote_not_working/comment_5_ebb7cc0e1c125765611014049d403d61._comment b/doc/bugs/STANDARD__95__IA_for_S3_remote_not_working/comment_5_ebb7cc0e1c125765611014049d403d61._comment new file mode 100644 index 000000000..73feda9a9 --- /dev/null +++ b/doc/bugs/STANDARD__95__IA_for_S3_remote_not_working/comment_5_ebb7cc0e1c125765611014049d403d61._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d" + subject="comment 5" + date="2015-12-12T05:28:51Z" + content=""" +Thanks for the clarification. I was referring to the Linux build. I might have been wrong about aws 0.13 being released. It is listed in the NixOS and Hackage package repos, but I don't see a 0.13.0 tag on the project's GitHub page, so maybe those other repos are packaging the nightly build of the master branch as version 0.13.0 while the final 0.13.0 hasn't been frozen yet. I will wait for the Debian repo to get updated (I could build it by hand but I like to rely on the package manager as I will otherwise forget to update the package in the future). It looks like Debian unstable lags the git repo tags by 1-2 months. +"""]] -- cgit v1.2.3