Log message:
recursive bump from gettext-lib shlib bump.

Log message:
Update to duplicity-0.5.20:
New in v0.5.20 (2009/08/28)
---------------------------
Bugs fixed this release:
408059  Failure due to _logger.log failure for content with special
        characters: TypeError decoding Unicode not supported
412667  "duplicity remove-older-than" asks for passphrase even though
        not required
418170  [PATCH] file names longer then 512 symbols are not supported

New in v0.5.19 (2009/08/06)
---------------------------
Fixed problem where Cygwin was returning -1 for the
hard max open file limit.
On process that complete before waitpid(), log them
and return zero as the process return status.
Make sure 'invalid packet (ctb=14)' from gpg is not
a fatal error.
Copy changes from trunk for duplicity translation.
Allow handling of unicode filenames in log messages.
Ignore unicode() translation errors in log messsages.

Log message:
Remove @dirrm entries from PLISTs

Log message:
Update to duplicity-0.5.18.

New in v0.5.18 (2009/05/20)
---------------------------
Added support for RackSpace's CloudFiles, cf+http.
Added support for Tahoe-LAFS
patch #6743: Tahoe backend for duplicity
Only half of this bug is fixed but it's still useful.
bug #21792: pipe call fails with an error OSError:
            [Errno 24] Too many open files
Changed from using ulimit external command to
 resource.getrlimit to check open files limit.

New in v0.5.17 (2009/05/04)
---------------------------
Removed one line of code left from some testing that I
 did that caused a crash when the target dir was empty
 and collection-status was requested.
Moved from using the df command to get temp space
 availability to Python's os.statvfs() call.  Not all
 df commands work the same way.
patch #6813: Making changelist easy to read
patch #6814: Ignore comments in filelists

New in v0.5.16 (2009/04/21)
---------------------------
bug #24825: duplicity warn on insufficient TMPDIR
            space availability and low max open
            file limits pre-backup.
bug #25594: wrong backup statistics
bug #25976: Password requested when not needed.
patch #6806: More graceful handling of old
             --short-filename files
Added tilde and variable expansion to the source or
target argument that is not a URL.

New in v0.5.15 (2009/04/09)
---------------------------
FTP backend was failing on PureFTPd when the "-x ''"
 option was removed from the second ncftpls popen, a fix
 that was implemented due to bug #24741.  This fix does
 the ls in one pass by extracting the last entry on the
 'ls -l' listing.
If a file is unreadable due to access rights or other
 non-fatal errors, put out error message and continue
 rather than dying messily with a traceback.
Added tilde '~' expansion and variable expansion in the
 options that require a filename.  You can now have this
 "--archive-dir=~/ArchDir/$SYSNAME" if you need it.  No
 expansion is applied to the source or target URL's.
Fixed problem I caused, again, where sys.exit() was
 trapping instead of exiting.  Added big note to not
 to do that again.

New in v0.5.14 (2009/04/02)
---------------------------
After email voting among known duplicity contributors,
 the decision was reached to revert to the GPL Version 2
 license, so with their consensus, duplicity is now under
 GPL Version 2.
Revert to calling NcFTP utilities (ls, get, put) directly
 rather than scripting ncftp via pexpect by reverting to the
 0.5.07 version of ftpbackend.py.
Changed fatal error regarding version 3.2.0 of ncftpput to
 warning level since it has been reported that the problem
 does not occur on most distributions.

Changed from log.Log with numbered log levels to log.Debug,
log.Info, log.Notice, log.Warn, log.FatalError.
The -vN option has not changed.  Verbosity may also be one
 of: character [ewnid], or word ['error', 'warning', 'notice',
 'info', 'debug'].  The default is 4 (Notice).  The options
 -v4, -vn, and -vnotice are functionally equivalent, as are
 the mixed-case versions, -vN, -vNotice, -vNOTICE.
Normalized include statements and tried to insure that all
 duplicity includes were from the duplicity module.
patch #6790: Add --exclude-if-present

New in v0.5.13 (2009/03/26)
---------------------------
Add more error detection to FTP backend.
Fix backends so sleep does not occur after last retry.
Fix so BackendException does not cause traceback except when
verbosity is at level 5 or higher (Info level).
Adjust log levels so some errors show up with default verbosity.
Fixed bug where an extra comma caused a traceback during a warning
 about unnecessary sig files.  Plus fixed print so the real filename
 would show up and not a Python object representation.
Add Changelog.GNU to website and distribution to add a bit of detail
 showing the CVS changes via rcs2log.  Added dist/mkGNUChangelog.sh.
bug #22908: Don't block gpg-agent
To fix the above, --use-agent was added as a command line option.
 When this is specified and asymetric encryption is enabled, then all
 GnuPG passphrases will come from the gpg-agent or equivalent program
 and no passphrase prompt will be issued.
bug #25787: Usernames with escaped @-sign are not handled properly
bug #25976: Password requested when not needed.
patch #6787: import duplicity.GnuPGInterface explicitly

New in v0.5.12 (2009/03/15)
---------------------------
bug #25838: Backup fails / ncftp - remote file already exists
With this fix we also get resume in ftp get/put.  If a put or
 get fails part of the way through, ncftp will resume on the
 next retry.
bug #25853: duplicity fails with boto passwords coming from ~/.boto
patch #6773: Make user name optional in rsync backend
GPG errors will no longer cause tracebacks, but will produce a
 log entry, from gpg, similar to the following:
===== Begin GnuPG log =====
gpg: BAD0BAD0: skipped: public key not found
gpg: [stdin]: encryption failed: public key not found
===== End GnuPG log =====
This will let the user know what really caused the GPG process
to fail, and what really caused errors like 'broken pipe'.

New in v0.5.11 (2009/03/08)
---------------------------
bug #25787: Usernames with @-sign are not handled properly
Bug #333057: GnuPGInterface prints exit statuses incorrectly
bug #25696: ncftp error w/0.5.09 -- nested target directories
bug #15664: When restoring backup: "OverflowError:
            long int too large to convert to int"
patch #6761: More robust pexpect handling of SSH authentication
patch #6762: Wrong exit() used for 2.3/2.4 Python

Log message:
Update to duplicity-0.5.10.

New in v0.5.10 (2009/03/01)
---------------------------
The default filename format has changed from W3 style to a long
numeric style, YYYYMMDDTHHMMSSZ, with no delimiters, thus is now
compatible with Windows/Samba filesystems.  The time is UTC, not
local, so there will be no timezone or daylight savings time issues.

Duplicity still recognizes the old long filename format, and will
continue incremental backup chains if found.  The old format is
still available via the --old-filenames option (pending deprecation).

Users of --short-filenames or --time-separator should stop using these
options on their next full backup.  The new filenames are compatible
with your system.

The following options are pending deprecation and will be removed in a
future release:
    --time-separator
    --short-filenames
    --old-filenames

bug #19988: Incompatibility to Samba/SMB share
bug #25097: Allow listing files from any time, not just current time
bug #25550: Error codes do not propagate from log to exit status
bug #25308: Signatures orphaned if from another time zone
Bug #229826: duplicity crashed with ValueError in port()

New in v0.5.09 (2009/02/17)
---------------------------
FTP is now driven with pexpect rather than NcFTP utilities.
This closes the following bugs (and solves other problems):
bug #24741: ncftpls -x '' causes failure on Yahoo FTP server
bug #23516: duplicity/ncftpget not closing unlinked files, ...
bug #25509: Logic error in imapbackend.py [IMAP_SERVER]
bug #25512: [Patch] Retry on Imap failure
bug #25530: commandline passwd not working

New in v0.5.08 (2009/02/02)
---------------------------
Turns out going backwards in the license is not as easy as
forwards.  Restoring GPLv3 license until consensus reached.

New in v0.5.07 (2009/01/31)
---------------------------
bug #25293: IOError: [Errno 22] Invalid argument
bug #25379: sys.exit() causes traceback and should not
bug #25403: 0.5.06 "manifests not equal, different volume numbers"
patch #6729: New imap backend. Replaces current gmail backend
patch #6730: Fix timing out for SSH backend
patch #6733: Improve error handling in imapbackend.py

Increase default volume size (--volsize) to 25M from 5M.  This
reduces the number of volumes to accomodate larger backups.

Reworked patch 6701 to list collection one at a time rather than
writing all as one huge list.  Was causing memeory problems when
the collections got large.

Fix backendtest.py so that empty URL's in config.py cause the
backend test to be skipped rather than erroring.  Added notes
in config.py.tmpl explaining the change.

Add/update copyright statements in all distribution source files
and revert duplicity to GPL version 2 license.

Original fix to disallow use of ncftpput 3.2.0 mistyped the ErrorCode
used and resulted in an error rather than an explanation.

New in v0.5.06 (2009/01/09)
---------------------------
Fix to deprecation warnings about sha and md5 modules.
Uses hashlib if available, otherwise original module.

Added loop to run-all-tests.sh to run all tests against all supported
versions of Python if available.  Looks for 2.3, 2.4, 2.5, 2.6.

Noah Spurrier has given us permission to distribute pexpect.py along
with duplicity, so this will no longer be an install requirement.

NcFTP version 3.2.0 will not work with duplicity since we require the
use of both -f and -C options on ncftpput.  3.1.9, 3.2.1+ work fine.
I put in error checks for this situation in the FTP backend code.

bug #25230: --include-globbing-filelist only including first entry.
bug #25239: Error during clean, wrong case in duplcicity
patch #6709: Report correct number of volumes when restoring
sr #106583: document the need to use the --force option

New in v0.5.05 (2008/12/30)
---------------------------
bug #25194: Duplicity 5.04 requires python-distutils-extra...

New in v0.5.04 (2008/12/27)
---------------------------
patch #6678: Add progress metering
patch #6686: Add error codes for all fatal errors
bug #25090: Typos and trailing whitespace in duplicity manpage
bug #24889: NCFTP cannot deal with some FTP servers
patch #6692: Print collection status in a machine-readable way
patch #6693: Some FatalError's don't have codes still
patch #6694: Log exceptions
patch #6695: Log filenames
patch #6696: Consolidate get_delta_iter and get_delta_iter_w_sig
patch #6697: Always log at least one progress during dry run
patch #6700: Make duplicity translatable
patch #6701: Make current-list command machine-readable
patch #6702: handle unknown errnos in robust.py

GPG was throwing "gpg: [don't know]: invalid packet (ctb=14)" and \ 
apparently
this is non-fatal.  There is a fix for this being rolled into GPG 2.x.
http://lists.gnupg.org/pipermail/gnupg-devel/2006-September/023180.html
Copied from collections.py.  Fix supplied by Simon Blandford \ 
<simon@onepointltd.com>

New in v0.5.03 (2008/11/17)
---------------------------
bug #24731: Documentation error: "if... if" in remove-older-than paragraph
bug #24775: Digest Auth for WebDAV backend
patch #6676: Raw delta stats aren't right for multivolumes
patch #6675: Add modelines
patch #6674: Add --log-* options to man page
patch #6673: Add --dry-run option
patch #6672: makedist doesn't ship util.py
patch #6670: Machine Readable Output
patch #6662: improve s3 backend error reporting
patch #6652: improve asynch scheduler (including the synchronous case)
patch #6642: make ParsedUrl() thread-safe with respect to itself
patch #6638: correct typo in reporting lack of sufficiently new boto backend
sr #106496: put install-from-cvs-notes in CVS-README
sr #106534: GMail backups aren't stored in the correct location

New in v0.5.02 (2008/09/21)
---------------------------
- Add -h option for help

- Change gpg logging so that logs are always collected.
The log is printed in the case of gpg IO errors.  Also,
verbosity level 5 or above (-v5) will print the logs.

patch #6297: Add IMAP/s/gmail support
bug #24260: backend.py missing re import
bug #24274: asyncscheduler.py missing sys import

New in v0.5.01 (2008/09/11)
---------------------------
bug #24234: Tabs Present In Source Files
bug #24223: WebDAV backend broken in 0.5.00
bug #24226: WebDAV Does Not Create Collection If Needed

New in v0.5.00 (2008/09/06)
---------------------------
Changes to unit tests:
  - resolve circular imports after backend reorg
  - resolve exception error import - now in errors.py
  - remove need for temp2.tar to be in CVS repository

bug #23988: scp destination fails if no username is specified
bug #23985: --no-encryption option does not work in 0.4.12
patch #6623: slightly augment tempdir cleanup logging
patch #6596: re-organize backend module structure
patch #6589: S3 european bucket support
patch #6353: Concurrency for volume encryption and upload.

Log message:
update to 0.4.12
changes:
-minimize the number of password prompts
-bugfixes

Log message:
update to 0.4.11
changes:
-restore a patch which got lost in 0.4.10, for S3 filestore
-fix for ssh uris with given portnumbers

Log message:
Update to duplicity-0.4.10.

New in v0.4.10 (2008/03/27):
bug #22728: FTP backend fails on empty directory
patch #6374: Duplicity --tempdir patch documentation.
patch #6375: Duplicity reports the epoch for a nonexistant last full backup date
patch #6380: add additional named logging levels
patch #6389: Possible Fix for pagefile.sys on Win32 systems
patch #6403: Restore by overwriting files/directories by using --force option
patch #6449: add additional debug level logging
patch #6453: handle absolute urls in webdav backend

Log message:
Update PYTHON_VERSIONS_COMPATIBLE
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.

Log message:
Update to version 0.4.9.  ChangeLog is extremely verbose; see
${WRKSRC}/CHANGES.  With this update comes Amazon S3 support provided
by the newly imported net/py-boto package.  This has not been tested yet,
however, as I do not have an S3 account.  Please let me know if this update
has resulted in any untoward effects.  Thanks.