Re: Issue with rsync 3.0.0 and iconv

2008-04-01 Thread Matt McCutchen
On Tue, 2008-04-01 at 01:59 -0700, Kurt Martinsen 543 wrote: > I have the same problem: > received request to transfer non-regular file: 88183 [sender] > rsync error: protocol incompatibility (code 2) at rsync.c(298) > [sender=3.0.0] > > Is it just the one file that gets discarded or is it the who

Re: Issue with rsync 3.0.0 and iconv

2008-04-01 Thread Kurt Martinsen 543
Is it just the one file that gets discarded or is it the whole process that stops at this point? Any plans on releasing a new binary version including this fix anytime soon? Regards, Kurt -- View this message in context: http://www.nabble.com/Issue-with-rsync-3.0.0-and-iconv-tp16239983p164169

Re: Issue with rsync 3.0.0 and iconv

2008-03-26 Thread Sergi Baila
Great, that was fast! Thanks a lot for your work Wayne. I'll test it asap. On Tue, Mar 25, 2008 at 6:58 PM, Wayne Davison <[EMAIL PROTECTED]> wrote: > On Sun, Mar 23, 2008 at 07:54:09PM +0100, Sergi Baila wrote: > > 2008/03/23 19:27:37 [3760] received request to transfer non-regular > file: 8630

Re: Issue with rsync 3.0.0 and iconv

2008-03-25 Thread Wayne Davison
On Sun, Mar 23, 2008 at 07:54:09PM +0100, Sergi Baila wrote: > 2008/03/23 19:27:37 [3760] received request to transfer non-regular file: > 86300 [sender] OK: thanks to Sergi's off-list debug info, I've fixed the problem. It was caused by a name that failed to convert on the sending side, and tha

Re: Issue with rsync 3.0.0 and iconv

2008-03-24 Thread Sergi Baila
Thanks for your answer Wayne, I've run the command with -vvv and got a 13 megs output. ;-) The file bzipped is just under 1M, I can send to you directly by email if you want. There seems to be certain unsync between the moment this line appears: received request to transfer non-regular file: 86

Re: Issue with rsync 3.0.0 and iconv

2008-03-23 Thread Wayne Davison
On Sun, Mar 23, 2008 at 07:54:09PM +0100, Sergi Baila wrote: > 2008/03/23 19:27:37 [3760] received request to transfer non-regular file: > 86300 [sender] This means either that file-list number 86300 is not matching up between the sender and the receiver, or that the data stream is somehow out of

Issue with rsync 3.0.0 and iconv

2008-03-23 Thread Sergi Baila
Hello there, I have a windows box (spanish locale, charset cp1252) which is backup to a linux server via rsync. Until now I've had problems with file names containing non us-ascii characters. Since the new stable version of rsync with support for iconv I've upgraded rsync on my linux (Debian) to 3