Hmmm, ok. My problem is that the file structure is actually generated by another application (in my case the Rails plugin attachment_fu). So re-syncing the source isn't really a fix. Is it possible that you can make the retrieval more "lenient" given this situation? I reckon that'd be worth a pint Thanks.

Ok, so a really stupid question - where do I get it from? I've just downloaded the version linked as "latest" and that identifies itself as 1.1.2 (and still has the same prob). Thanks!

Hi - I sent you an email through with steps to reproduce and an example tar file as requested. I haven't heard anything - did you get it ok?

Thanks

Hi, I seem to be having a similar problem - can you tell me what I'm doing wrong? I'm using s3sync.rb version 1.1.2. So, I've got this in MYBUCKET:

./s3cmd.rb list MYBUCKET
--------------------
category_images/
category_images/2
category_images/2/ring.jpg
photos/

Note: the photo's dir is empty.

So if I run s3sync.rb -r MYBUCKET: /root/testing/

I get the output:

S3 command failed:
head MYBUCKET category_images
With result 404 Not Found
S3 command failed:
get_stream MYBUCKET photos  #<File:0x2acc74f57150>
With result 404 Not Found

I get the files, but end up with bad permissions:
d--x-wx--T 4 root root 4096 May 26 21:51 category_images

How should I sync the entire content of an s3 bucket back down?

Thanks,

Nick