duplicity-team team mailing list archive

[Kenneth Loafman <kenneth@xxxxxxxxxxx>]

The par2 patches were merged into the 0.7 series, but that series has fallen
behind 0.6 and needs serious work.  My last attempt at merging the recent
changes met with disaster, so I'm inclined to restart on par2, use some of
the ideas, but rewrite the code from scratch.  For now, treat 0.7 as very
experimental.

On Sat, Jun 4, 2011 at 11:50 AM, gwern <gwern0@xxxxxxxxx> wrote:

> What is the status of these par2 patches? It's been almost 2 years since
> the last comment; has the functionality been incorporated into
> duplicity? (I've been generating the PAR2 files for my duplicity backups
> manually and it's fairly annoying.)
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/426282
>
> Title:
>  [PATCH] par2 creating support
>
> 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
>

-- 
You received this bug notification because you are a member of
duplicity-team, which is a bug assignee.
https://bugs.launchpad.net/bugs/426282

Title:
  [PATCH] par2 creating support

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