The problem with these specific files seems to have gone away after
upgrading to 4.3.1 so indeed perhaps was not a Charset issue as you
and I have both started to include, but rather was/is part of the same
root cause(s) that I have highlighted in my other bug reports.
That being said, after upgra
Jeff,
I tried recreating this but wasn't able to get the error you reported. The
file name I created piped to "od -c" prints 'r 351 p o n s e .
d o c' (the 351 is octal, hex e9).
When I set ClientCharset to utf8, I do indeed get your first error (cannot
convert filename). But
Craig Barratt wrote at about 23:00:28 -0700 on Monday, June 24, 2019:
> Jeff,
>
> I don't think it's the same issue, even though the final state looks
> similar. In this case, since the file name isn't encoded correctly, I
> suspect that when rsync goes back to actually open it, it does appe
Jeff,
I don't think it's the same issue, even though the final state looks
similar. In this case, since the file name isn't encoded correctly, I
suspect that when rsync goes back to actually open it, it does appear to be
missing since the file name byte string doesn't point to the file (ie, it
(i
Hi Craig,
I just tried a backup with:
$Conf{ClientCharset} = '';
But now instead of the previous error:
[sender] cannot convert filename: user1/docs/r\#351ponse.doc (Invalid or
incomplete multibyte or wide character)
I now get the (familiar?) error:
rsync_bpc: fstat "user1/docs/r\#351p
Jeff,
I suspect you'll get the same error if you use native rsync and tell it to
convert utf8 to utf8 (eg, add '--iconv=utf8,utf8' to your native rsync
command).
Since you don't need any conversion, you should set $Conf{ClientCharset} to
an empty string. That should cause rsync to no longer atte
Craig Barratt via BackupPC-users wrote at about 13:59:46 -0700 on Sunday, June
23, 2019:
> The error you are getting is when rsync_bpc is trying to use iconv to
> convert the client file name encoding to utf8 (which is the native format
> that BackupPC on the server).
>
> What is $Conf{Clien
The error you are getting is when rsync_bpc is trying to use iconv to
convert the client file name encoding to utf8 (which is the native format
that BackupPC on the server).
What is $Conf{ClientCharset} set to for this host? If it is empty then
rsync_bpc should skip any charset conversion, so I a
Michael Stowe wrote at about 03:35:13 + on Sunday, June 16, 2019:
> On 2019-06-15 19:20, backu...@kosowsky.org wrote:
> > I am running backuppc 4.3.0 on Linux Ubuntu 18.04
> >
> > I have a file copied over from an old Windows installation to my Linux
> > server with name:
> >
> > -rwx-
On 2019-06-15 19:20, backu...@kosowsky.org wrote:
I am running backuppc 4.3.0 on Linux Ubuntu 18.04
I have a file copied over from an old Windows installation to my Linux
server with name:
-rwx-- 1 user1 user1 28672 May 11 2005 'r'$'\351''ponse.doc'
This file gives an error under backupp
I am running backuppc 4.3.0 on Linux Ubuntu 18.04
I have a file copied over from an old Windows installation to my Linux
server with name:
-rwx-- 1 user1 user1 28672 May 11 2005 'r'$'\351''ponse.doc'
This file gives an error under backuppc as follows:
[sender] cannot convert filename:
11 matches
Mail list logo
