Follow-up Comment #7, bug #25542 (project duplicity):
I read comment 2 and you were right about where to break it up, in
dup_temp.py. I have not thought about where to reassemble it, but it would
probably be best to look at the place it's downloaded into a temp. Catch it
there and reassemble into a single file. That way you won't have to mess with
collections.py.
Since the ~/.duplicity directory is expected to be around between backups
now, the only reason to download it from remote is if that dir has been
destroyed somehow, so even a special case might do it, kind of a preparatory
step before duplicity begins. The local copy would still be one file,
assuming it was still there.
I really have not thought about this much. Backing up to IMAP is such a
special use case for duplicity that it just has not been on my mental radar.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?25542>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Duplicity-tracker mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/duplicity-tracker
