Description:

Upgraded to duplicity 0.6.11 on Arch x86_64. When run, duplicity immediately fails with this python trace:

Traceback (most recent call last):
File "/usr/bin/duplicity", line 1245, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1238, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1124, in main
action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python2.7/site-packages/duplicity/commandline.py", line 927, in ProcessCommandLine
backup, local_pathname = set_backend(args[0], args[1])
File "/usr/lib/python2.7/site-packages/duplicity/commandline.py", line 820, in set_backend
globals.backend = backend.get_backend(bend)
File "/usr/lib/python2.7/site-packages/duplicity/backend.py", line 153, in get_backend
return _backends[pu.scheme](pu)
File "/usr/lib/python2.7/site-packages/duplicity/backends/rsyncbackend.py", line 52, in __init__
del os.environ['RSYNC_RSH']
File "/usr/lib/python2.7/os.py", line 496, in __delitem__
del self.data[key]
KeyError: 'RSYNC_RSH'

Steps to reproduce:

Install Duplicity 0.6.11, run program.


*** WORK AROUND ***
I read on another forum that this is a known bug in the duplicity package. The work around is to manually set the RSYNC_RSH environment variable to the full path for the 'rsync' executable, e.g.:

export RSYNC_RSH=/usr/bin/rsync


This is a little annoying, but I wanted the work around to be in the Arch database in case other people run into it, and to get this bug fixed.