duplicity-team team mailing list archive
-
duplicity-team team
-
Mailing list archive
-
Message #00146
[Bug 426282] Re: [PATCH] par2 creating support
I'm assigning this to the entire duplicity-team since we'll need all of
your help in getting this into 0.7-series. I'm working on getting the
initial patch to work correctly with all of the unit tests, in some
cases changing the tests to fit, then I'll push a version to 0.7-series,
close to what Plamen had in the patch.
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => In Progress
** Changed in: duplicity
Milestone: None => 0.7.00
** Changed in: duplicity
Assignee: (unassigned) => duplicity-team (duplicity-team)
--
[PATCH] par2 creating support
https://bugs.launchpad.net/bugs/426282
You received this bug notification because you are a member of
duplicity-team, which is a bug assignee.
Status in duplicity - Bandwidth Efficient Encrypted Backup: In Progress
Bug description:
OK, this add support for creating par2 recovery files for every file that gets uploaded to the backend.
- can be enabled by passing --par2. If the backend already contains par2 files there is no need to pass the --par2 option.
- the par2 files are created just before the upload of the file so this will not break the asynchronous mode.
- all par2 files are preserved in the local cache and uploaded to the backend.
todo:
- add comments and logging
- add support for customizing the pa2 options currently 20% redundancy is used which might be an overkill or too little for someone
- don't use os.system and add error handling.
- add support for recovery.
Code review will be greatly appreciated. There are some very ugly hacks with temp files