13. mars 2008 03:39
> To: Mojca Miklavec
> Cc: rsync@lists.samba.org; Tevfik Karagülle; Taco Hoekwater
> Subject: Re: (cw)rsync 3.0.0 incompatible with 2.6.9
>
> On Wed, 2008-03-12 at 20:57 +0100, Mojca Miklavec wrote:
> > On Wed, Mar 12, 2008 at 4:46 PM, Matt McCutchen wro
On Wed, 2008-03-12 at 20:57 +0100, Mojca Miklavec wrote:
> On Wed, Mar 12, 2008 at 4:46 PM, Matt McCutchen wrote:
> > 3. Have cwRsync 3.0.0 users pass RSYNC_ICONV=- or --no-iconv .
>
> That's what has been suggested by Tevfik Karagülle, but it's ugly as
> it cannot be written in a portable way. (
On Wed, Mar 12, 2008 at 4:46 PM, Matt McCutchen wrote:
> On Wed, 2008-03-12 at 16:02 +0100, Mojca Miklavec wrote:
> > I have updated the windows binary for rsync to 3.0.0 (cwrsync), and
> > now I get the following error:
> >
> > receiving file list ... rsync: on remote machine: --iconv=.: unkno
On Wed, 2008-03-12 at 17:11 +0100, Tevfik Karagülle wrote:
> I am a little bit confused now. What's best ? An rsync with iconv enabled or
> not ?
>
> I thought that iconv support could be useful to handle file names with
> foreign characters. However, I see now that an iconv-enabled rsync has som
On Wed, 2008-03-12 at 16:02 +0100, Mojca Miklavec wrote:
> I have updated the windows binary for rsync to 3.0.0 (cwrsync), and
> now I get the following error:
>
> receiving file list ... rsync: on remote machine: --iconv=.: unknown option
> rsync error: requested action not supported (code 4) at
Hello,
This seems like rather serious issue to me.
I have updated the windows binary for rsync to 3.0.0 (cwrsync), and
now I get the following error:
receiving file list ... rsync: on remote machine: --iconv=.: unknown option
rsync error: requested action not supported (code 4) at clientserver.c
