lp:~scowcron/duplicity/ftp_password_pexpect
- Get this branch:
- bzr branch lp:~scowcron/duplicity/ftp_password_pexpect
Branch merges
- duplicity-team: Pending requested
-
Diff: 22 lines (+3/-8)1 file modifiedduplicity/backends/_ssh_pexpect.py (+3/-8)
Related bugs
Related blueprints
Branch information
Recent revisions
- 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.
- 913. By Kenneth Loafman
-
* Merged in lp:~townsend/duplicity/fix-1161599-2
- The fix in revno. 912 didn't take into account that the parameter "body"
passed into request() is overloaded, so when it was NULL or of a type other
than file, it would fail. This checks if "body" is of type "file" before
actually seek()'ing back to the beginning of the file. - 912. By Kenneth Loafman
-
* Merged in lp:~tblue/duplicity/paramiko-1.10.0
- This fixes bug #1156746, making the Paramiko backend compatible with
Paramiko 1.10.0. It keeps compatibility with older Paramiko versions. - 911. By Kenneth Loafman
-
* Merged in lp:~ed.so/duplicity/verify.data
- add switch --compare-data, to selectively enable formerly always disabled
data comparison on verify runs
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