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/lib64/python2.7/site-packages/duplicity/commandline.py", line 927, in ProcessCommandLine backup, local_pathname = set_backend(args[0], args[1]) File "/usr/lib64/python2.7/site-packages/duplicity/commandline.py", line 820, in set_backend globals.backend = backend.get_backend(bend) File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 153, in get_backend return _backends[pu.scheme](pu) File "/usr/lib64/python2.7/site-packages/duplicity/backends/rsyncbackend.py", line 52, in __init__ del os.environ['RSYNC_RSH'] File "/usr/lib64/python2.7/os.py", line 496, in __delitem__ del self.data[key] KeyError: 'RSYNC_RSH' This error is not reproducable with earlier versions of duplicity. Reproducible: Always Steps to Reproduce:
Please post your `emerge --info' in a comment.
Created attachment 256774 [details] cave info duplicity
I see you have trouble reading English. OK, THANKS. NOW >ATTACH< THE ENTIRE BUILD LOG AS A >FILE<. DO NOT PASTE IT IN A COMMENT AT ALL. Get it?
(comment #1) > Please post your `emerge --info' in a comment. (comment #3) > I see you have trouble reading English. > > OK, THANKS. NOW >ATTACH< THE ENTIRE BUILD LOG AS A >FILE<. DO NOT PASTE IT IN A > COMMENT AT ALL. > > Get it? Please watch your language. If you would have said "buildlog", I would have attached it. But you said "emerge --info", so I attached (the paludis-equivalent of) that. I didn't *paste* anything but the *output* of duplicity which is reasonably short. Attachment of buildlog is following.
Created attachment 257216 [details] duplicity buildlog
Created attachment 257233 [details, diff] rsyncbackend-environ.patch Does my patch solve your issue? I just hit it too.. But it's more a upstream bug.
(In reply to comment #6) > Created an attachment (id=257233) [details] > rsyncbackend-environ.patch > > Does my patch solve your issue? I just hit it too.. But it's more a upstream > bug. > No it doesn't. I had to correct it (there's a colon missing after the if-statement), but even that produces the same exception (originating in the line with the new if-statement): 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/lib64/python2.7/site-packages/duplicity/commandline.py", line 927, in ProcessCommandLine backup, local_pathname = set_backend(args[0], args[1]) File "/usr/lib64/python2.7/site-packages/duplicity/commandline.py", line 820, in set_backend globals.backend = backend.get_backend(bend) File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 153, in get_backend return _backends[pu.scheme](pu) File "/usr/lib64/python2.7/site-packages/duplicity/backends/rsyncbackend.py", line 52, in __init__ if os.environ['RSYNC_RSH']: File "/usr/lib64/python2.7/UserDict.py", line 23, in __getitem__ raise KeyError(key) KeyError: 'RSYNC_RSH' As I said, I'm not sure if I did everything right, so I'll attach the ebuild I used and the modified patch
Created attachment 257327 [details] slightly modified patch there was a colon missing in the last patch
Created attachment 257328 [details] Ebuild used to patch the sources with the patch posted a minute ago
PS: The file /usr/lib64/python2.7/site-packages/duplicity/backends/rsyncbackend.py is indeed modified, so the patch seems to have worked.
Yeah, sorry for the missing colon. Make sure the rsyncbackend.pyc and .pyo are *not* older than the rsyncbackend.py.
No, they all have the same age % ls -l /usr/lib64/python2.7/site-packages/duplicity/backends ... -rw-r--r-- 1 root root 6.4K Dec 16 16:43 rsyncbackend.py -rw-r--r-- 1 root root 5.6K Dec 16 16:43 rsyncbackend.pyc -rw-r--r-- 1 root root 5.6K Dec 16 16:43 rsyncbackend.pyo ...
There is also a upstream bug. The patch is slightly different, try it instead please. https://bugs.launchpad.net/duplicity/+bug/681980
(In reply to comment #13) > There is also a upstream bug. The patch is slightly different, try it instead > please. > https://bugs.launchpad.net/duplicity/+bug/681980 > It works!
What's the status, does the patch work for you, too? Can you release a patched duplicity-0.6.11-r1 in portage?
New in v0.6.12 (2011/03/08) ---------------------------- Bugs closed in this release: 681980 Duplicity 0.6.11 aborts if RSYNC_RSH not set 0.6.13 is in the tree.
