lp:~germar/duplicity/par2

Created by Germar and last modified
Get this branch:
bzr branch lp:~germar/duplicity/par2
Only Germar can upload to this branch. If you are Germar please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Germar
Project:
Duplicity
Status:
Merged

Recent revisions

923. By Germar

Merged in lp:duplicity

922. By Germar

add documentation to manpage
rename ~par2wrapperbackend.py

921. By Germar

Merged in lp:duplicity

920. By Germar

add par2 wrapper backend

919. By Kenneth Loafman

* Applied duplicity-ftps.patch from https://bugs.launchpad.net/duplicity/+bug/1104069
  - Don't try to delete an empty file list.

918. By Kenneth Loafman

* Applied blocksize.patch from https://bugs.launchpad.net/duplicity/+bug/897423
  - New option --max-blocksize (default 2048) to allow increasing delta blocksize.

917. By Kenneth Loafman

* Merged in lp:~jnoster/duplicity/dpbx-added
  - The application key was approved as "production" one after some changes to the code
    to suit the requirements of Dropbox team (the keys are now obfuscated, for instance).

916. By Kenneth Loafman

* Merged in lp:~juan-f/duplicity/progress
  - From time ago, there are people asking for a progress bar estimation in duplicity.
    There is even a script that circumvents the issue, getting info from the log so as
    to estimate the progress status ( https://github.com/quentin/Duplicity-progress )
    but does not give enough feedback and the estimation is rather plain.
  - I have developed a set of heuristics that gather information from the deltas and
    the transfer ratios of the backend so as to forecast % of progress, estimation of
    remaining time and average speed, for both full and incremental backup uploads.
  - The current implementation works for boto backend, but to port the other backends
    to use this feature would be quite easy (we can discuss the details if interested).
  - The algorithm is activated by the --progress command line flag, and will perform a
    first-pass dry-run to collect evidence for all the deltas. Next it will trigger the
    real upload, while a thread statistically estimates the ratio of changes and
    compression for the data in/out, and uses these ratios to forecast time remaining
    and % of completion.
  - The progress data will be logged each 3 seconds, or the --progress-rate flag.

915. By Kenneth Loafman

* Merged in lp:~tblue/duplicity/paramiko-fix-delete-retry
  - This fixes bug #1115715, which is really annoying. Basically it makes
    using the Paramiko backend with the default settings impossible.

914. By Kenneth Loafman

Actually merge in lp:~tblue/duplicity/paramiko-1.10.0 as previously reported.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:duplicity/0.6
This branch contains Public information 
Everyone can see this information.

Subscribers