On 26 March 2013 09:47, Vladimir Stavrinov <vstavrinov@gmail.com> wrote:
On Tue, Mar 26, 2013 at 09:37:11AM +0200, Michael Wood wrote:

>    Someone reported recently that the latest 1.5.0 alpha fixed this issue
>    for them.

Thanks. But I am sticking with debian package.

Well, then it might be best to report the bug to Debian.

Since the elapsed time was not very important to me, I worked around the issue like this:

--- s3cmd-1.1.0-beta3/s3cmd    2012-01-12 04:28:20.000000000 +0200
+++ /usr/bin/s3cmd    2012-11-05 19:10:59.000000000 +0200
@@ -306,7 +306,7 @@
         speed_fmt = formatSize(response["speed"], human_readable = True, floating_point = True)
         if not Config().progress_meter:
             output(u"File '%s' stored as '%s' (%d bytes in %0.1f seconds, %0.2f %sB/s) %s" %
-                (unicodise(full_name_orig), uri_final, response["size"], response["elapsed"],
+                (unicodise(full_name_orig), uri_final, response["size"], response.get("elapsed", 999999999),
                 speed_fmt[0], speed_fmt[1], seq_label))
         if Config().acl_public:
             output(u"Public URL of the object is: %s" %

--
Michael Wood <esiotrot@gmail.com