Your message dated Sun, 2 Mar 2008 14:03:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#166183: rsync: doesnt work if there are spaces in
filenames
has caused the Debian Bug report #166183,
regarding rsync: doesnt work if there are spaces in filenames
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
166183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=166183
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: rsync
Version: 2.5.5-0.1
Severity: normal
here it is
$ rsync remotehost:'ciao prova' .
link_stat ciao : No such file or directory
link_stat prova : No such file or directory
client: nothing to do: perhaps you need to specify some filenames or
the --recursive option?
rsync error: partial transfer (code 23) at main.c(594)
(since Windows people use a lot of spaces, this makes it quite
difficult to use rsync to move thei files around)
btw: scp has the same problem
bye and thanks
a.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux tonelli 2.4.19-k7 #1 Thu Aug 8 23:19:38 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages rsync depends on:
ii libc6 2.2.5-14.3 GNU C Library: Shared libraries an
ii libpopt0 1.6.2-7 lib for parsing cmdline parameters
--
Andrea Mennucc
"E' un mondo difficile. Che vita intensa!" (Tonino Carotone)
--- End Message ---
--- Begin Message ---
On Fri 10 Feb 2006, Wayne Davison wrote:
> This is not really a bug, but the documented way rsync currently works.
> It uses unescaped spaces to allow the user to ask for multiple arguments
> from the remote host, and thus requires that filenames with spaces be
> escaped in some shell-compatible manner.
>
> Another way to avoid the problem is to use the --files-from option, even
> if you're just asking for one file. This works fine because filenames
> read via --files-from are used literally, with no special handling
> needed for space-containing names.
As the problem has been adequately explained, including workarounds,
I'm now closing this bug.
Paul Slootman
--- End Message ---
