Hi Craig,
the answer by Andrew was in another thread, might gone unnoticed:
> The error is due to a typo in robust.py on line 77
> ("e.errno" should be "exc.errno").
@Andrew: in v1.30 Main.py, line 202 the '--' was not adopted from my patch,
so using '--use-compatible-timestamps' option currently does not work w/o
below change.
elif opt == "use-compatible-timestamps":
I have: elif opt == "--use-compatible-timestamps":
I just upgraded a couple of machines to 1.3.0
Below is a traceback when running on a standard script of mine: (Used to
work with 1.1.15)
It's backing up from a Windows server to a unix box. The script runs on
the unix box.
Any thoughts? (The first line is output from my script, the rest is from
rdiff-backup)
Cheers,
Craig
2009-01-07 11:54:36 Backing up plsbs_backup::d:/users to
/mnt/backup/serverbackup/plsbs/users with args:=20
Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 30, in <module>
rdiff_backup.Main.error_check_Main(sys.argv[1:])
File "/usr/lib/python2.5/site-packages/rdiff_backup/Main.py", line
309, in error_check_Main
errmsg =3D robust.is_routine_fatal(exc)
File "/usr/lib/python2.5/site-packages/rdiff_backup/robust.py", line
77, in is_routine_fatal
elif isinstance(exc, EnvironmentError) and e.errno
errno.ENOTCONN:
NameError: global name 'e' is not defined
Oliver
_______________________________________________
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
