Your message dated Fri, 3 Aug 2007 17:40:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#307242: rsync: now replaces non-ASCII character with
numerical values
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: rsync
Version: 2.6.4-2
Severity: important
I've used two identical Sarge systems, both using UTF-8.
Using rsync (over ssh), syncing (or listing the contents) from one
system to the other, non-ASCII characters get replaced with '??', eg:
[EMAIL PROTECTED]:~$ rsync system2:~/test_åäö_test
drwxr-xr-x 72 2005/05/02 02:39:30 test_??????_test
The result above is new since version 2.6.4-2 and makes logs from
backup-scripts (using rsync) almost unreadable when lots of files and
directories with, in my case swedish, non-ASCII character are being processed.
When the backup-script also relies on the resulting log for further
processing, this bug completly breaks it as corresponding directories/files
doesn't exist on the filesystem.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686-smp
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Versions of packages rsync depends on:
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii libpopt0 1.7-5 lib for parsing cmdline parameters
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed 01 Aug 2007, Paul Slootman wrote:
> On Sun 25 Sep 2005, Per Andersson wrote:
> >
> > Is this something that's being worked on upstream? Is there a workaround?
>
> Upstream has fixed this now, and characters that can be displayed in the
> current locale will be displayed correctly. I've tested version 2.6.9.
> Please confirm this for me, so that I can close this bug if you agree.
[EMAIL PROTECTED] bounces, so closing this bug now.
Paul Slootman
--- End Message ---
