We are seeing this in versions of Python prior to 2.5. The traceback
appears to be triggered by the use of sys.exit() and is not a real
problem, but a bit nervous making. It will be fixed in the next
release, but for now, please just ignore it.
...Thanks,
...Ken
Roberto Pereyra wrote:
Hi all !
I just instaled the latest duplicity version and have this error when run it:
I'm using:
Thanks for any help
boto-1.6b.tar.gz
duplicity-0.5.06.tar.gz
GnuPGInterface-0.3.2.tar.gz
librsync-0.9.7-2.el5.rf.i386.rpm
librsync-devel-0.9.7-2.el5.rf.i386.rpm
and Centos 5
address@hidden [/]# duplicity
Command line error: Expected 2 args, got 0
Enter 'duplicity --help' for help screen.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 583, in ?
with_tempdir(main)
File "/usr/bin/duplicity", line 577, in with_tempdir
fn()
File "/usr/bin/duplicity", line 504, in main
action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python2.4/site-packages/duplicity/commandline.py",
line 510, in ProcessCommandLine
args = parse_cmdline_options(cmdline_list)
File "/usr/lib/python2.4/site-packages/duplicity/commandline.py",
line 296, in parse_cmdline_options
command_line_error("Expected %d args, got %d" % (num_expect, len(args)))
File "/usr/lib/python2.4/site-packages/duplicity/commandline.py",
line 304, in command_line_error
log.ErrorCode.command_line)
File "/usr/lib/python2.4/site-packages/duplicity/log.py", line 164,
in FatalError
sys.exit(code)
SystemExit: 2
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk