Your message dated Wed, 09 Jan 2008 13:40:09 -0500
with message-id <[EMAIL PROTECTED]>
and subject line No longer seems to be broken
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: rdiff-backup
I tried backing up my home directory onta a vfat filesystem.
rdiff-backup seems like it has quoted chararacter support that should
have dealt with this. However there was a file in my home directory
with multiple * characters in the name. Only one of these was quoted.
So rdiff-backup executed a rename system call with a destination file
name including *, which failed on the vfat filesystem.
--Sam
--- End Message ---
--- Begin Message ---
I just executed the following using the latest version of rdiff-backup:
mkdir foo
touch foo/***.txt
touch foo/foo***.txt
touch foo/f*o*o*.txt
rdiff-backup --override-chars-to-quote "*;" foo bar
ls -l bar
and got:
total 0
-rw-r--r-- 1 owsla owsla 0B Jan 9 13:27 ;042;042;042.txt
-rw-r--r-- 1 owsla owsla 0B Jan 9 13:27 f;042o;042o;042.txt
-rw-r--r-- 1 owsla owsla 0B Jan 9 13:28 foo;042;042;042.txt
drwx------ 11 owsla owsla 374B Jan 9 13:29 rdiff-backup-data
so it certainly looks like multiple *'s are currently being escaped
properly.
Sam, can you please reopen this bug and provide more details
(specifically, the output of `rdiff-backup -v5 ...`, the name of the
file that was improperly quoted, and the contents of the
rdiff-backup-data/chars_to_quote file on the destination).
Thanks,
Andrew
--- End Message ---
