Re: [Duplicity-talk] duplicity 0.6.12 / AssertionError during incremental backup

[Michael Schneider]

In fact, I had several duplicates (vol 48, 49, 50, 51, 52, but not vol 53 and 54: 

Fo reach duplicate volume, one was empty and one was correct. The empty ones look like this:

Content-Type: multipart/mixed; boundary="===============7249155798656478530=="
MIME-Version: 1.0
From: v2
Subject: duplicity-inc.20110614T181901Z.to.20110619T192531Z.vol48.difftar.gpg

--===============7249155798656478530==
Content-Type: application/binary
MIME-Version: 1.0
Content-Transfer-Encoding: base64


--===============7249155798656478530==--

I have no idea why only 5 of 54 volumes where affected. It seems (list order in my client) that the empty sets were created after the correct ones.

Deleting the empty files resolved the problem.

-Mike