Re: [Duplicity-talk] Found signatures but no corresponding backup files.

[Marcus Gustafsson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kenneth Loafman skrev:
> Please try this with RC12.  On RC9 we moved from BitBucket to Boto as
> the S3 backend processor and this may correct your problem.
> 
> As the first run, please run 'duplicity --cleanup --force ...' to clean
> up any incomplete backups.

I installed the new version, but ran into a small problem. It seems the
GnuPG option --bzip2-compress-level=9 is not supported on the GnuPG
coming with RHEL4. I removed it from gpg.py which fixed the problem. I
assume that there is a better way to do it, so I won't include a patch
for it.

Thanks for the help Ken!
I hope it will have solved the problem.

Regards,
  Marcus

> Marcus Gustafsson wrote:
>> Hello!
>>
>> We have just started using duplicity to backup one of our mailservers to
>> S3, but we have recently gotten problems that whenever we take a full
>> backup 2 incremental backups later the backups seems to become corrupted.
>> I googled on the error message, but didn't manage to find out anything
>> obvious. Anyone have a good idea of where I should start looking?
>>
>> We are running 0.4.3.RC2 and the commands are as follows:
>>
<snip run examples>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGw87OzYC0ZmFVS9sRAogJAKC36ydgbvda8rEXmRkoD7uDQjHDowCfdoVm
n0hwWW0KdZttarqEwmaDo8w=
=6ch4
-----END PGP SIGNATURE-----