On Jan 5, 2009, at 6:06 AM, Dominic wrote:
... but I do get an error with rdiff-backup 1.2.4 when running from
a *Windows* client (to Linux-based rdiff-backup server) thus:
C:\>rdiff-backup -r 0D [email protected]::archives/
mydocs/myfile.docx myfile.docx
Traceback (most recent call last):
File "rdiff-backup", line 30, in <module>
File "rdiff_backup\Main.pyc", line 307, in error_check_Main
File "rdiff_backup\robust.pyc", line 77, in is_routine_fatal
NameError: global name 'e' is not defined
Is this the known bug with Windows escaping (Savannah #25041) or
something different? If it is, is the only solution to move to
1.3.0? (Strangely the last line of my error messages is the same as
Ryan reported in 1.3.0 ('long filename error' thread))
Hi Dominic,
Due to the typo in robust.py on line 77 ("e.errno" should be
"exc.errno") we don't know what error is causing your restore to fail.
I will release 1.2.5 shortly so that we see better error messages.
After that, feel free to try again, and we can see what went wrong.
Andrew
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
