Duplicity backs directories by producing encrypted tar-format volumes and
uploading them to a remote or local file server. Because duplicity uses
librsync, the incremental archives are space efficient and only record the
parts of files that have changed since the last backup. Because duplicity
uses GnuPG to encrypt and/or sign these archives, they will be safe from
spying and/or modification by the server.
WWW: http://duplicity.nongnu.org
===> The following configuration options are available for duplicity-devel-0.8.11:
B2=on: Backblaze B2 backend
DOCS=on: Build and/or install documentation
FTP=on: FTP backend
FTPS=on: FTPS backend
GDOCS=off: Google Docs backend
NLS=on: Native Language Support
S3=on: Amazon S3 backend
====> GnuPG support: you have to select exactly one of them
GNUPG=off: Use GnuPG 1
GNUPG2=on: Use GnuPG 2
===> Use 'make config' to modify these settings
The following backends are supported by duplicity itself, but will
require manual installation of their respective dependencies because
they are not yet available in the ports tree:
- The Dropbox backend
- The HSI backend
- The mega backend for mega.co.nz
- The swift backend for OpenStack Object Storage
- The tahoe backend for Tahoe-LAFS
Please refer to upstream duplicity documentation for information on
the use of these backends.
For gnupg 2 insert "pinentry-mode loopback" into ~/.gnupg/gpg.conf
and "allow-loopback-pinentry" into ~/.gnupg/gpg-agent.conf
Some fixes related to gnupg handling were made in v0.7.12.
Please visit the following URL for more information:
http://duplicity.nongnu.org/CHANGELOG
Remove expired ports:
2020-03-29 security/w3af: Uses deprecated version of Python
2020-03-30 sysutils/duplicity-devel: Obsolete now, use sysutils/duplicity
instead
2020-03-31 net-mgmt/tornova: Use EOL'd Python 2.7
2020-03-31 audio/py-ogg: Unmaintained, uses EOLed python27
2020-03-31 net-mgmt/onionlauncher: Use EOL'd Python 2.7
2020-03-31 databases/mongodb34: EOL January 2020; See
https://www.mongodb.com/support-policy
2020-03-31 graphics/sane-frontends: Unmaintained upstream, no consumers left
2020-03-31 lang/ruby24: Move to a new version (lang/ruby26 or above). Ruby 2.4
is in security maintenance phase and planned for EOL on March 31, 2020
2020-03-31 databases/pgpool: Reached EOL at 2019-10-31, please use pgpool-II-35
or higher
2020-03-31 net/pygopherd: Unmaintained, uses EOLed python27
databases/mongodb34-tools: Part of expired MongoDB 3.4
sysutils/duplicity-devel: Update to 0.8.11
Changelog: https://launchpad.net/duplicity/+milestone/0.8.11
Simplify port removing setup.py patch, which was removing all testing
references. Now is necessary remove missing files from TMPPLIST.
These files are removed in the setup.py install target, between building
and installing.
sysutils/duplicity-devel: Change Google Drive backend dependency to py-pydrive
py-pydrive is the default gdocs backend on duplicity and py-gdata
don't support Python 3.
PR: 243055
Submitted by: Arnaud de Prelle <arnaud@pnzone.net>
Add sysutils/duplicity-devel: Backup tool that uses librsync and GnuPG
This is the current development release.
Duplicity backs directories by producing encrypted tar-format volumes and
uploading them to a remote or local file server. Because duplicity uses
librsync, the incremental archives are space efficient and only record the
parts of files that have changed since the last backup. Because duplicity
uses GnuPG to encrypt and/or sign these archives, they will be safe from
spying and/or modification by the server.
WWW: http://duplicity.nongnu.org
sysutils/duplicity-devel is far out of date, and has been marked IGNORE
for a long time. The former maintainer has stepped down, so remove
this stale port.
Feature safe: yes
- Bring in commit r665 from upstream which fixes a
bug (613448) in the ftpbackend which prevents destination
directories being created.
PR: ports/149923
Submitted by: Jase Thew <freebsd@beardz.net>
Approved by: peter.schuller@infidyne.com (maintainer)
