Re: [Duplicity-talk] Fwd: AssertionError on every attempt

[Bruce Merry]

On 8 June 2015 at 18:43,  <address@hidden> wrote:
> On 08.06.2015 18:31, Bruce Merry wrote:
>> Hi
>>
>> (apologies if this shows up twice - my first attempt was without
>> subscribing to the list, and since it didn't show up in the list
>> archives I'm assuming it went to the bit-bucket)
>>
>> I've somehow managed to get my Google Drive into a state where every
>> time I run duplicity I get the error below. This occurred after I
>> started a full backup, which crashed on volume 27, restarted it, and
>> it later crashed again (I don't have the errors messages from those
>> backups saved, sorry). I'm using the PyDrive backend, specifically
>> https://code.launchpad.net/~bmerry/duplicity/pydrive-regular. I've
>> tried
>> - running duplicity cleanup (hits the same assertion)
>> - wiping out the .cache/duplicity directory to force resync (resyncs,
>> then hits the same assertion)
>>
>> I've since noticed that I have two copies of
>> duplicity-full.20150607T094026Z.vol27.difftar.gpg in my Google Drive,
>> which probably explains why I get the assertion error, but I'm not
>> sure how to safely recover from this without ending up with a
>> corrupted backup. Is it safe to just delete one of them?

<snip>

> are you sure that you have two identically named files on the backend? can 
> you send a file listing of some kind?

Yes, I've double-checked it in the GUI. I used a quick PyDrive script
to get a list of all files in the drive which is attached, but it
doesn't distinguish what directory everything is in (Google Drive
seems only loosely tied to the idea of a filesystem), which also shows
the duplicate.

I've also discovered
https://bugs.launchpad.net/duplicity/+bug/1462862, which I think is
most likely the same thing I'm seeing. My (partial) manifest also has
two Volume 27: lines, with the same starting and ending path but
different SHA1 sums.

Is it safe to manually delete all the files on the remote and in my
cache directory corresponding to this backup set (*20150607T094026Z*)
and just start the full backup from scratch?

Thanks
Bruce
-- 
Dr Bruce Merry
bmerry <@> gmail <.> com
http://www.brucemerry.org.za/
http://blog.brucemerry.org.za/

filelist.txt
Description: Text document