should be fixed in 1.1.3

By the way, this error should have been caught in 1.1.3
the NoMethodError thing happens when using --progress and the file is not readable on the local side.

This happens when it's removed, or when it just errors out such as when it's a unix pipe or what not.

should be fixed.

Try 1.1.3:
http://s3sync.net/forum/index.php?topic=60.msg226#msg226

IMPORTANT!
Pursuant to http://s3sync.net/forum/index.php?topic=49.0 , the tar.gz now expands into its own sub-directory named "s3sync" instead of dumping all the files into the current directory.

Changes:
2007-06-02
Version 1.1.3
In the case of commands of the form:
   s3sync -r somedir somebucket:
The root directory node in s3 was being stored as "somedir/" instead of "somedir"
which caused restores to mess up when you say:
   s3sync -r somebucket: restoredir
The fix to this, by coincidence, actually makes s3fox work even *less* well with
s3sync.  I really need to build my own xul+javascript s3 GUI some day.

Also fixed some of the NoMethodError stuff for when --progress is used
and caught Errno::ETIMEDOUT
----------

Was busy during the week.  I'll take a look today though!

I doubt that the permissions thing is related to the directory thing. 

Can you create a tar.gz of your test data (with correct permissions) and send it to me (email address is in the README)

Trippy idea.

Are you using the latest version?  It used to have some problems with directory creation, but that should be long gone by now.

The only other problem is if the directory node for "home" is missing from the s3 side.  This can happen if you selectively only backed up certain subdirectories of "/home/..." but not "/home" itself.

In this case, on the local machine you'll need to create any top level dirs that don't exist on the s3 side.  so for example
mkdir /root/home
and then your first command would go fine.

Sweet!  Anyone test this?

Thanks for the feedback.

The reason I think there aren't all that many "success stories" is that people tend to be happy when it works, and go do other stuff instead of posting here =)

ferrix, short and to the point responses like that usually suggest that someone's been irritated by something they consider to be a stupid  question or unreasonable request, such that it doesn't warrant anything more. 

Understood, however in this case I'm just really busy, and wanted to say something rather than leave you guessing what I might be planning to do about it!

I don't mean adding streaming to S3 ruby lib, everyone's done that by now .  As you sort of allude, I think you really do need to add some code to net/http to get the *capability* of streaming at all.  And I don't know how easy it is to backport.

I am not even going to consider anything pre-1.8.4 as supported, since that was the minimum version I wrote the original code to!  If someone wants to back-port, I will be happy to maintain a "compatibility" release here.

As background: is mac not capable of easily running anything less archaic than .2?

This will not be attempted.

Read readme please.  1.8.2 cannot work; lacks streaming.