lp:~tblue/duplicity/paramiko-fix-delete-retry
- Get this branch:
- bzr branch lp:~tblue/duplicity/paramiko-fix-delete-retry
Branch merges
- duplicity-team: Pending requested
-
Diff: 41 lines (+13/-11)1 file modifiedduplicity/backends/_ssh_paramiko.py (+13/-11)
Related bugs
Bug #1115715: Paramiko backend: delete() always fails if --num-retries > 1 | Medium | Fix Released |
Related blueprints
Branch information
Recent revisions
- 909. By Tilman Blumenbach
-
Paramiko backend, delete(): Terminate when all files have been deleted successfully.
Previously, delete() would delete the entire list of files (as expected) and
then *always* go into its "retry on error" loop, i. e. it would try to delete
the (now non-existant) files _again_, which obviously always caused it to fail
eventually. - 907. By Kenneth Loafman
-
* Merged in lp:~mterry/duplicity/py3rsync
- This branch lets one build the _librsync module with Python 3. You can't
really do anything useful with it, but it's a nicely-isolated piece to add
Python 3 support for.
- The changes are a mix of modernization and #ifdef logic.
- All tests still pass in Python 2.7 and 2.4. I tested manually that the module
worked as expected in Python 3. - 906. By Kenneth Loafman
-
* Merged in lp:~mterry/duplicity/pygi
- Python bindings for the gobject stack (used in the gio backend) have changed
from static to dynamically-generated bindings. The old static bindings are
deprecated. So here's a branch to change the gio backend from old to new ones. - 905. By Kenneth Loafman
-
* Merged in lp:~ed.so/duplicity/webdav.manpage
- explanation of webdav changes above - 904. By Kenneth Loafman
-
* Merged in lp:~ed.so/duplicity/webdav.fix-retry
- added ssl certificate verification (see man page)
- more robust retry routine to survive ssl errors, broken pipe errors
- added http redirect support - 903. By Kenneth Loafman
-
* Merged in lp:~mterry/duplicity/static-corruption
- This branch fixes three possible ways a backup could get data-corrupted.
Inspired by bug 1091269.
A) If resuming after a volume that ended in a one-block file, we would
skip the first block of the next file.
B) If resuming after a volume that ended in a multi-block file, we would
skip the first block of the next file.
C) If resuming after a volume that spanned a multi-block file, we would
skip some data inside the file.
- A and B are because when finding the right place in the source files to
restart the backup, the iteration loop didn't handle None block numbers
very well (which are used to indicate the end of a file).
- C is what bug 1091269 talks about. This was because data block sizes would
get smaller as the difftar file got closer and closer to the volsize.
Standard block sizes were 64 * 1024. But say we were close to the end of
the difftar... When resuming, duplicity doesn't know the custom block sizes
used by the previous run, so it uses standard block sizes. And it doesn't
always match up, as you can imagine. So we would leave chunks of data out
of the backed up file.
- Tests added for these cases.
- This branch is called 'static-corruption' because all these issues occur
even when the source data doesn't change. I still think there are some
corruption issues when a file changes in between duplicity runs. I haven't
started looking into that yet, but that's next on my list.
- C only happened without encryption (because the gpg writer function already
happened to force a constant data block size). A and B happened with or
without encryption. - 902. By Kenneth Loafman
-
* Fixed 1091269 Data corruption when resuming with --no-encryption
- Patches from Pascual Abellan that make block size consistent and
that add no-encryption option to manual-ctrl-c- test.sh.
- Modified gpg.py patch to use 64k block size so unit test passes. - 901. By Kenneth Loafman
-
* Merged in lp:~ed.so/duplicity/u1_and_manpage
- Manpage
- document Ubuntu One required python libs
- added continuous contributors and backend author notes
- U1backend
- lazily import non standard python libs, fixes
http://article. gmane.org/ gmane.comp. sysutils. backup. duplicity. general/ 5753
- fix "not bytearray" prevents PUT with python 2.6
- don't hang after putting in credentials (cause it silently retries in background)
but go through with backup - 900. By Kenneth Loafman
-
* Merged in lp:~ed.so/duplicity/manpage
- Clear up PASSPHRASE reusage as sign passphrase. Minor fixes.
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