1
2013-01-18 Kenneth Loafman <kenneth@loafman.com>
3
* Merged in lp:~duplicity-team/duplicity/po-updates
5
* Prep for 0.6.21 release
7
2013-01-18 Kenneth Loafman <kenneth@loafman.com>
9
* Merged in lp:~ed.so/duplicity/webdav.fix-retry
10
- added ssl certificate verification (see man page)
11
- more robust retry routine to survive ssl errors, broken pipe errors
12
- added http redirect support
13
* Merged in lp:~ed.so/duplicity/webdav.manpage
14
- explanation of webdav changes above
15
* Merged in lp:~mterry/duplicity/pygi
16
- Python bindings for the gobject stack (used in the gio backend) have changed
17
from static to dynamically-generated bindings. The old static bindings are
18
deprecated. So here's a branch to change the gio backend from old to new ones.
19
* Merged in lp:~mterry/duplicity/py3rsync
20
- This branch lets one build the _librsync module with Python 3. You can't
21
really do anything useful with it, but it's a nicely-isolated piece to add
23
- The changes are a mix of modernization and #ifdef logic.
24
- All tests still pass in Python 2.7 and 2.4. I tested manually that the module
25
worked as expected in Python 3.
27
2013-01-07 Kenneth Loafman <kenneth@loafman.com>
29
* Merged in lp:~mterry/duplicity/static-corruption
30
- This branch fixes three possible ways a backup could get data-corrupted.
31
Inspired by bug 1091269.
32
A) If resuming after a volume that ended in a one-block file, we would
33
skip the first block of the next file.
34
B) If resuming after a volume that ended in a multi-block file, we would
35
skip the first block of the next file.
36
C) If resuming after a volume that spanned a multi-block file, we would
37
skip some data inside the file.
38
- A and B are because when finding the right place in the source files to
39
restart the backup, the iteration loop didn't handle None block numbers
40
very well (which are used to indicate the end of a file).
41
- C is what bug 1091269 talks about. This was because data block sizes would
42
get smaller as the difftar file got closer and closer to the volsize.
43
Standard block sizes were 64 * 1024. But say we were close to the end of
44
the difftar... When resuming, duplicity doesn't know the custom block sizes
45
used by the previous run, so it uses standard block sizes. And it doesn't
46
always match up, as you can imagine. So we would leave chunks of data out
47
of the backed up file.
48
- Tests added for these cases.
49
- This branch is called 'static-corruption' because all these issues occur
50
even when the source data doesn't change. I still think there are some
51
corruption issues when a file changes in between duplicity runs. I haven't
52
started looking into that yet, but that's next on my list.
53
- C only happened without encryption (because the gpg writer function already
54
happened to force a constant data block size). A and B happened with or
57
2013-01-02 Kenneth Loafman <kenneth@loafman.com>
59
* Fixed 1091269 Data corruption when resuming with --no-encryption
60
- Patches from Pascual Abellan that make block size consistent and
61
that add no-encryption option to manual-ctrl-c-test.sh.
62
- Modified gpg.py patch to use 64k block size so unit test passes.
64
2013-01-01 Kenneth Loafman <kenneth@loafman.com>
66
* Merged in lp:~ed.so/duplicity/u1_and_manpage
68
- document Ubuntu One required python libs
69
- added continuous contributors and backend author notes
71
- lazily import non standard python libs, fixes
72
http://article.gmane.org/gmane.comp.sysutils.backup.duplicity.general/5753
73
- fix "not bytearray" prevents PUT with python 2.6
74
- don't hang after putting in credentials (cause it silently retries in background)
75
but go through with backup
77
2012-12-22 Kenneth Loafman <kenneth@loafman.com>
79
* Merged in lp:~ed.so/duplicity/webdav.fix-retry
80
- bugfix: webdav retrying broke on ERRORS like "error: [Errno 32] Broken pipe" in
81
socket.pyas reported here https://answers.launchpad.net/duplicity/+question/212966
82
added a more generalized 'retry_fatal' decorator which makes retrying backend
84
* Merged in lp:~ed.so/duplicity/manpage
85
- Clear up PASSPHRASE reusage as sign passphrase. Minor fixes.
87
2012-12-17 Kenneth Loafman <kenneth@loafman.com>
89
* Merged in lp:~lenharo-h/duplicity/duplicity
90
- Generate encrypted backups without revealing the user's key id
91
via option --hidden-encrypt-key
92
* Merged in lp:~mterry/duplicity/u1-utf8
93
- Make sure u1backend returns filenames as utf8
94
* Merged in lp:~carlos-abalde/duplicity/gdocs-backend-gdata-2.0.16.-upgrade
95
- Upgrade of GoogleDocs backend to python gdata lib >= 2.0.15:
96
Stop using get_everything method.
98
2012-11-19 Kenneth Loafman <kenneth@loafman.com>
100
* Merged in lp:~ed.so/duplicity/lftp.netrc
101
- Allow .netrc auth for lftp backend
102
* Merged in lp:~mterry/duplicity/946988
103
- This fixes bug 946988 by not duplicating the checks for when we should ask
104
for the password (those same checks are done more correctly inside
105
get_passphrase). And add a test to reproduce the bug.
107
2012-11-10 Kenneth Loafman <kenneth@loafman.com>
109
* Merged in lp:~satwell/duplicity/caching
110
- Add a cache for password and group lookups. This significantly improves
111
runtime with very large password and group configurations.
112
* Merged in lp:~ed.so/duplicity/manpage
113
- more formatting fixes, clarifications in sections EXAMPLES, FILE SELECTION
115
2012-11-03 Kenneth Loafman <kenneth@loafman.com>
117
* Merged in lp:~mterry/duplicity/u1-oauthlib
118
- As the Ubuntu packager for duplicity, I would prefer u1backend.py
119
used oauthlib instead of oauth. oauthlib is well maintained upstream
120
(unlike oauth), has a python3 port (for the future), and is in Ubuntu
121
main (so is oauth right now, but hopefully in the future we can drop
122
it to universe, in which case duplicity can't use it anymore).
123
* Merged in lp:~mterry/duplicity/delete-new-sig-in-cache
124
- In duplicity 0.6.20, we fixed bug 1031269. This means that we no longer
125
leave sig files on the remote location. Leaving sig files on the remote
126
location also caused a bug with deleting cache files. Code used to leave
127
remote new-sig but delete the locale cache new-sig; this meant that we would
128
keep downloadoing the new-sig all the time from remote. We had worked around
129
that by just not deleting the new-sig in the cache, which was sort of the
130
wrong side of that problem to tackle. Now that we handle the remote
131
new-sigs better (by deleting them), I don't think we need this code anymore.
132
Patch by az@debian.org.
133
* Merged in lp:~mterry/duplicity/u1-ascii-error
134
- Fix for u1backend unicode error. Patch by Paul Barker.
137
2012-10-29 Kenneth Loafman <kenneth@loafman.com>
139
* Merged in lp:~ed.so/duplicity/24syntaxfix
140
- fix python 2.4 vs 2.5 syntax error
1
142
2012-10-28 Kenneth Loafman <kenneth@loafman.com>
3
144
* Remove dist/mkGNUchangelog script.
added
removed
Changelog.GNU
