lp:~verb/duplicity/boto-gcs

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:duplicity/0.6 at revision 922

duplicity-team: Pending requested 2013-08-02

Diff: 208 lines (+64/-12)

5 files modified

bin/duplicity.1 (+25/-2)
duplicity/backends/_boto_single.py (+14/-10)
testing/manual/backendtest.py (+13/-0)
testing/manual/config.py.tmpl (+10/-0)
testing/tests/test_tarfile.py (+2/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1030868: Support Google Cloud Storage

Medium

Fix Released

Link a bug report

Related blueprints

923. By Lee Verberne on 2013-07-26

Add documentation for GCS to duplicity.1

922. By Lee Verberne on 2013-07-26

Add config template for testing boto backend with GCS

921. By Lee Verberne on 2013-07-19

Add support for Google Cloud Storage to boto backend (single threaded only)

920. By Lee Verberne on 2013-07-12

explicitly set umask in test_tarfile.py

tar honors umasks which causes the unittest to fail if a more restrictive mask
(e.g. 027) is set. This change sets umask explicitly.

919. By Kenneth Loafman on 2013-04-27

* 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 on 2013-04-27

* 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 on 2013-04-27

* 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 on 2013-04-27

* 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 on 2013-04-27

* 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 on 2013-04-27

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