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.

Log message:
Update "duplicity" package to version 0.4.3. Changes since version 0.4.2:
Move get_password() to Backend class to standardize.
- Fix problem with ftpBackend to create target directory
  if needed.  Note: this creates only one level.
- Dropped ssh-command and added ssh-options to allow users
  to add options to the scp and sftp commmands.
- Removed use of tempfile.TemporaryFile().  This fixes the
  restore problem on Windows that was due to Python bug
  1776696 reported on Sourceforge.
- Fixed Debian Bug#437694: Make bzip2 compression optional.
  The default is not to do bzip2 compression.  To use bzip2
  add the following command line option:
  --gpg-options='--compress-algo=bzip2 --bzip2-compress-level=9'
  Note: do not add spaces in the string value.
- Fixed bug 20764 - unable to use port in ssh backend.
  https://savannah.nongnu.org/bugs/?20764
- Remove ssh_command option, add ssh_options.  This adds
  options to the scp and sftp commands that are used by
  the ssh backend.
- Change ssh backend to send 'quit' instead of EOF when
  using sftp.  This allows it to run under cron as long
  as the password is supplied non-interactively.
- Change ssh backend to not pass :port part of URL to
  scp or sftp.  We already supply -oPort=xx for port.

Log message:
Update duplicity to 0.4.2.
Patch provided by Martin Wilke via PR 34574.
And also work with python24, so add 24 to PYTHON_VERSIONS_ACCEPTED.

Log message:
Over 1200 files touched but no revisions bumped :)

RECOMMENDED is removed. It becomes ABI_DEPENDS.

BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.

BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.

BUILDLINK_DEPENDS does not change.

IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".

Added to obsolete.mk checking for IGNORE_RECOMMENDED.

I did not manually go through and fix any aesthetic tab/spacing issues.

I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.

I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.

As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.

As discussed on tech-pkg.

I will commit to revbump, pkglint, pkg_install, createbuildlink separately.

Note that if you use wip, it will fail!  I will commit to pkgsrc-wip
later (within day).

Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.