Path to this page:
Subject: CVS commit: pkgsrc/sysutils/duplicity
From: Thomas Klausner
Date: 2012-09-05 12:05:43
Message id: 20120905100543.82FC7175DD@cvs.netbsd.org
Log Message:
Update to 0.6.19, based on patch by Steven Sartorius in PR 46903.
New in v0.6.19 (2012/05/22)
---------------------------
Enhancements:
- lots of work on the man page to clean up requirements, etc.
- use empty listbody for enhanced webdav compatibility
- initial folder creation on backend does not result in a ResponseNotReady anymore
- add ssh_config support (/etc/ssh/ssh_config + ~/.ssh/config) to paramiko sshbackend
- add missing_host_key prompt to new sshbackend similar to ssh procedure
- added --ssh-backend parameter to switch between paramiko,pexpect
- allow answering gio mount questions (albeit naively)
- if the gio backend wants to ask a question during its mount phase, it \
previously just aborted.
- a couple more warning error codes that Deja Dup is interested in noticing.
- ssh paramiko backend respects --num-retries now
- set retry delay for ssh backends to 10s
- ssh pexpect backend
+ sftp part does not claim 'Invalid SSH password' although it's only \
'Permission denied' now
+ sftp errors are now more talkative
- gpg.py
+ commented assert which broke otherwise working verify run
Bugs closed in this release:
588541 Connection failed, please check your password: Login dialog cancelled
Merges:
lp:~ed.so/duplicity/0.6-manpage
lp:~ed.so/duplicity/0.6-webdav_fixes
lp:~carlos-abalde/duplicity/gdocs-backend-gdata-2.0.16.-upgrade.
lp:~ed.so/duplicity/0.6-ssh_add_missinghostkey
lp:~ed.so/duplicity/0.6-readd_sshpexpect
New in v0.6.18 (2012/02/29)
---------------------------
Enhancements:
- fix extraneous '.py' in botobackend.py include
- tests: add delay between backups to avoid assertion error
- tests: use backup source that is more likely to be larger than 1M compressed
- tests: make other-filesystem check more robust against certain directories \
being mounts or not
- resuming an incremental results in a 'Restarting backup, but current \
encryption settings do not match original settings' error because curtime is \
incorrectly set away from previous incremental value
- added option to not compress the backup, when no encryption is selected
- always delay a little bit when a backend gives us errors
- Don't cache TarInfo files. Tests still pass, so I don't believe we need the \
members cache (and in the old tarfile.py, we didn't cache either).
- Adding --file-prefix option so different sets of backups can be stored in the \
same bucket. See blueprint at \
https://blueprints.launchpad.net/duplicity/+spec/file-prefix-option
- two changes that help the test suite pass
- raise log level on backend import failure so it will be visible under default \
conditions
- file /etc/motd may not exist in test environment. Use __file__ instead to \
point to a known plaintext source file.
- some code/import changes to make the ssh and boto backends compatible with \
Python 2.4.
- some changes to make roottest.py compatible with the new dir structure.
Bugs closed in this release:
884638 Python 2.5 / boto error
908228 possible memory leak
909031 SSH-Backend: Creating dirs separately causes a permissons-problems
916689 multipart upload fails on python 2.7.2
929465 UnsupportedBackendScheme: scheme not supported in url: \
scp://u123@u123.example.com/foo/
930727 ftpsbackend should respect num_retries for ftp commands
931175 duplicity crashes when PYTHONOPTIMIZE is set
Merges:
lp:~mterry/duplicity/always-delay
lp:~mterry/duplicity/memleak
lp:~mterry/duplicity/nopexpect
lp:~mterry/duplicity/resume-inc
lp:~mterry/duplicity/testfixes
lp:~nguyenqmai/duplicity/file-prefix-option
lp:~tobias-genannt/duplicity/nocompress
New in v0.6.17 (2011/11/25)
---------------------------
Enhancements:
- Added --rsync-options flag to allow user to pass options to rsync at will
- Added --s3-use-multiprocessing to select the new s3 multiprocessing backend.
Default is to use the single processing backend. A helper, filechunkio.py,
requires Python 2.6+, so this option is not usable in earlier versions.
Bugs closed in this release:
411145 Misleading error message: "Invalid SSH password"
871875 File ... was corrupted during upload.
878220 UnsupportedBackendScheme: scheme not supported in url: s3+http
878964 Resuming a backup with a different password should throw an error
881070 Bugfix for S3 multipart upload on 0.6.16
881727 duplicity 0.6.16 lists all backup sets as incomplete
885670 Duplicity fails to add incremental backups to chain...
Merges:
lp:~mterry/duplicity/check-passphrase-on-restart
lp:~moss-d/duplicity/rsync-options
Files: