Currently error commands that do not return a body cause s3cmd to output an ugly backtrace. This change checks to see if the data field of the response is non-empty before calling `getTreeFromXml` on it. An example of an offending command is using `s3cmd info` on a nonexistent object.
Added S3 static site support for Amazon CloudFront invalidation on sync.
Follow symlinks, when requested, drop recursion detection.
Don't report "Disabled MD5 check for FILE" when --no-check-md5 used
…sed. If statement is still true if file fails md5 check.
Recursion detection on symlinks was too restrictive. It would detect the following as recursion: dir/ main-1234/ file1 file2 main -> main-1234 This is clearly not a recursion and a common pattern, eg when hosting package repositories. Python's os.walk also does not do recursion detection. So lets behave like Python stdlib.
By the way fixes a crash with: s3cmd put /xyz/big-file s3://bucket/ > /dev/null Reported by HanJingYu
* S3/PkgInfo.py: Updated to 1.1.0-beta3 * s3cmd.1: Regenerated.
Multipart-uploaded files don't have a valid MD5 sum in their ETag. We can detect it and disable MD5 comparison when deciding whether to sync these files. In such a case only the size (and later on a timestamp) is compared.
Apparently in Py2.4 the Exception class doesn't have 'message' attribute.
Sadly there are two "magic" modules for python with different APIs. Improving compatibility wrapper to better handle both.
Fixing KeyError when copying multiple keys (SourceForge bug 3091912)
When you use 's3cmd cp' to copy multiple keys (without using the recursive flag) you get a Key Error. s3cmd cp s3://source-bucket/prefix* s3://target-bucket Logged here: http://sourceforge.net/tracker/?func=detail&aid=3091912&group_id=178907&atid=887015 and here: https://bugs.launchpad.net/ubuntu/+source/s3cmd/+bug/523586
Reported by Andy McGregor
* S3/PkgInfo.py: Updated to 1.1.0-beta2 * NEWS: Updated. * s3cmd.1: Regenerated.