This is a bug in upstream s3cmd. As there is no planned fix, we can try to suppress the issue or switch to boto.
This is a bug in upstream s3cmd. As there is no planned fix, we can try to suppress the issue or switch to boto.