Fixed in upstream master branch.

On Fri, Aug 2, 2013 at 6:44 PM, Jonah Schwartz <> wrote:
I got the following errors trying to sync to s3. I reverted to v1.0.1 and things work. 

[ec2-user@ip-10-46-59-183 mixpanel]$ s3cmd sync * s3://dotandbo-analytics/mixpanel-dump/
WARNING: python-magic is not available, guessing MIME types based on file extensions only
mixpanel-2013-03-07.dump -> s3://dotandbo-analytics/mixpanel-dump/mixpanel-2013-03-07.dump  [part 1 of 3, 15MB]
 15728640 of 15728640   100% in    4s     3.34 MB/s  done
mixpanel-2013-03-07.dump -> s3://dotandbo-analytics/mixpanel-dump/mixpanel-2013-03-07.dump  [part 2 of 3, 15MB]
 15728640 of 15728640   100% in    4s     3.37 MB/s  done
mixpanel-2013-03-07.dump -> s3://dotandbo-analytics/mixpanel-dump/mixpanel-2013-03-07.dump  [part 3 of 3, 19kB]
 20178 of 20178   100% in    0s   411.50 kB/s  done

    An unexpected error has occurred.
  Please report the following lines to:

Problem: KeyError: 'size'
S3cmd:   1.1.0-beta2

Traceback (most recent call last):
  File "/usr/bin/s3cmd", line 2006, in <module>
  File "/usr/bin/s3cmd", line 1950, in main
  File "/usr/bin/s3cmd", line 1211, in cmd_sync
    return cmd_sync_local2remote(args)
  File "/usr/bin/s3cmd", line 1192, in cmd_sync_local2remote
    total_size += response["size"]
KeyError: 'size'

    An unexpected error has occurred.
    Please report the above lines to:

Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.