On Sat, Mar 28, 2009 at 9:53 AM, Russell Clemings
<address@hidden> wrote:
Since upgrading to duplicity-0.5.11 I've had several problems with backup to s3. Here's the first.
Both of these fail consistently with the error below:
/usr/local/bin/duplicity remove-all-but-n-full 1 --force ${DEST}
/usr/local/bin/duplicity cleanup --force --tempdir=/s3backup --encrypt-key=${GPG_KEY} --sign-key=${GPG_KEY} ${DEST}
Traceback (most recent call last):
File "/usr/local/bin/duplicity", line 589, in ?
with_tempdir(main)
File "/usr/local/bin/duplicity", line 582, in with_tempdir
fn()
File "/usr/local/bin/duplicity", line 510, in main
globals.archive_dir).set_values()
File "/usr/local/lib/python2.4/site-packages/duplicity/collections.py", line 557, in set_values
self.warn(sig_chain_warning)
File "/usr/local/lib/python2.4/site-packages/duplicity/collections.py", line 626, in warn
+ "\n" + "\n".join(self.other_sig_names),
TypeError: bad operand type for unary +
The environment is:
duplicity-0.5.11
boto-1.4c
cPanel 11.24.4-S33345 - WHM 11.24.2 - X 3.9
CENTOS 4.7 i686 on virtuozzo
Thanks in advance for any help.
rac