duplicity 3.2.1.dev0__tar.gz → 3.2.1.dev2__tar.gz

{duplicity-3.2.1.dev0 → duplicity-3.2.1.dev2}/CHANGELOG.md

@@ -1,9 +1,77 @@
 
-(Unreleased) / 2026-08-10
+(Unreleased) / 2026-08-20
 =========================
 
 
 
+rel.3.2.1.dev2 / 2026-08-20
+===========================
+
+ * [`77c5107e`](https://gitlab.com/duplicity/duplicity/-/commit/77c5107e):new: Add get_version() to librsync to retrieve underlying library version
+ * [`b839f2c8`](https://gitlab.com/duplicity/duplicity/-/commit/b839f2c8):new: Add pure Python librsync implementation using ctypes as fallback
+ * [`ba7957c3`](https://gitlab.com/duplicity/duplicity/-/commit/ba7957c3):new: Add coverage configuration and Makefile targets for testing.
+ * [`855c6f1c`](https://gitlab.com/duplicity/duplicity/-/commit/855c6f1c):chg: Remove outdated comment for `python3-gnupg` in `debian/control`
+ * [`22fae925`](https://gitlab.com/duplicity/duplicity/-/commit/22fae925):chg: Sync README files in `setup.py` and clean up verbosity flags
+ * [`978355b4`](https://gitlab.com/duplicity/duplicity/-/commit/978355b4):chg: Enable verbose mode in debian/rules
+ * [`626cdccb`](https://gitlab.com/duplicity/duplicity/-/commit/626cdccb):chg: Remove redundant `apt` commands in `debian/rules`
+ * [`ba71d094`](https://gitlab.com/duplicity/duplicity/-/commit/ba71d094):chg: Update setuptools to >=61.0.0 in dev dependencies and `debian/rules`
+ * [`2b55864a`](https://gitlab.com/duplicity/duplicity/-/commit/2b55864a):chg: Simplify `gnupg` import logic in `gpg.py`
+ * [`80abbd02`](https://gitlab.com/duplicity/duplicity/-/commit/80abbd02):chg: Adjust dependencies in `requirements.txt` and `debian/control`
+ * [`df52d45b`](https://gitlab.com/duplicity/duplicity/-/commit/df52d45b):chg: Add `python3-gnupg` as a build dependency in `debian/control`
+ * [`057c7d0a`](https://gitlab.com/duplicity/duplicity/-/commit/057c7d0a):chg: Update doc cleanup pattern in `debian/rules`
+ * [`4eaee861`](https://gitlab.com/duplicity/duplicity/-/commit/4eaee861):chg: Update doc cleanup to remove `duplicity-*` files in `debian/rules`
+ * [`7cd8ddb6`](https://gitlab.com/duplicity/duplicity/-/commit/7cd8ddb6):chg: Add `get_data_files` for dynamic data file handling in `setup.py`
+ * [`e9bf8843`](https://gitlab.com/duplicity/duplicity/-/commit/e9bf8843):chg: Simplify doc handling by removing outdated duplicity docs
+ * [`4bc93712`](https://gitlab.com/duplicity/duplicity/-/commit/4bc93712):chg: Update dependencies, streamline configs, and refine CI
+ * [`ca78d6c5`](https://gitlab.com/duplicity/duplicity/-/commit/ca78d6c5):chg: Update release-prep script to use `check_tags`
+ * [`60ae51f3`](https://gitlab.com/duplicity/duplicity/-/commit/60ae51f3):chg: Update release-prep script to fix tag removal and file refs
+ * [`45495e09`](https://gitlab.com/duplicity/duplicity/-/commit/45495e09):chg: Update pipeline triggers for push, web, and merge request events
+ * [`f8fc71e3`](https://gitlab.com/duplicity/duplicity/-/commit/f8fc71e3):chg: Improve process in `setup.py` and release prep script
+ * [`f36c9922`](https://gitlab.com/duplicity/duplicity/-/commit/f36c9922):chg: Refactor versioning and metadata handling
+ * [`84afa6f2`](https://gitlab.com/duplicity/duplicity/-/commit/84afa6f2):chg: Refactor string concatenations to f-strings across codebase
+ * [`480cbc23`](https://gitlab.com/duplicity/duplicity/-/commit/480cbc23):chg: Clean up and refactor `pyproject.toml` and `Makefile`
+ * [`42d4838d`](https://gitlab.com/duplicity/duplicity/-/commit/42d4838d):chg: Rewrite `makechangelog` script in Python
+ * [`1dee9e31`](https://gitlab.com/duplicity/duplicity/-/commit/1dee9e31):chg: b2backend prefer b2sdk.v3
+ * [`4f4e052e`](https://gitlab.com/duplicity/duplicity/-/commit/4f4e052e):chg: Cleanup some minor issues
+ * [`1e0a97dc`](https://gitlab.com/duplicity/duplicity/-/commit/1e0a97dc):chg: Format with Black/PEP8 and ensure file flush before rename
+ * [`22da1a0d`](https://gitlab.com/duplicity/duplicity/-/commit/22da1a0d):fix: Resolve PEP8 style issues and whitespace in backend and main modules
+ * [`06858c9a`](https://gitlab.com/duplicity/duplicity/-/commit/06858c9a):fix: Replace `os.system` calls with safer Python alternatives.
+ * [`da745307`](https://gitlab.com/duplicity/duplicity/-/commit/da745307):fix: Add --ignore-installed flag for pip in Dockerfiles
+ * [`883cca1e`](https://gitlab.com/duplicity/duplicity/-/commit/883cca1e):fix: restore issue: AssertionError: (b'keys', [...]) not empty
+ * [`aa0b23e7`](https://gitlab.com/duplicity/duplicity/-/commit/aa0b23e7):fix: Replace `log.FatalError` with `raise errors.FatalError`.
+ * [`c3a45713`](https://gitlab.com/duplicity/duplicity/-/commit/c3a45713):fix: Add support for "sync" action and handle passphrase checks.
+ * [`db99858e`](https://gitlab.com/duplicity/duplicity/-/commit/db99858e):fix: Enhance error handling and debug logging in Python modules
+ * [`dbb899ad`](https://gitlab.com/duplicity/duplicity/-/commit/dbb899ad):fix: Use 'python-gnupg' instead of our 'gpginterface.py'.
+ * [`4d6e9f8c`](https://gitlab.com/duplicity/duplicity/-/commit/4d6e9f8c):fix: PCABackend GET URL needs prefix if one is defined
+ * [`d7cd05d8`](https://gitlab.com/duplicity/duplicity/-/commit/d7cd05d8):fix: Could not release lockfile
+ * [`fcbe3a7a`](https://gitlab.com/duplicity/duplicity/-/commit/fcbe3a7a):fix: Enforce --force requirement for destructive operations
+ * [`c6c8b26a`](https://gitlab.com/duplicity/duplicity/-/commit/c6c8b26a):fix: Enhance BackupSet.delete signature cleanup and fix lock release
+ * [`3f0ab55b`](https://gitlab.com/duplicity/duplicity/-/commit/3f0ab55b):fix: Prevent premature deletion of full backups during incremental starts
+ * [`9819e4d4`](https://gitlab.com/duplicity/duplicity/-/commit/9819e4d4):fix: Add get_last_continuous_volume for reliable backup resumption
+ * [`5d737d07`](https://gitlab.com/duplicity/duplicity/-/commit/5d737d07):fix: Postpone metadata promotion to prevent orphaned cache files
+
+rel.3.2.0.1 / 2026-08-15
+========================
+
+ * [`3865b348`](https://gitlab.com/duplicity/duplicity/-/commit/3865b348):chg: Add `python3-gnupg` as a build dependency in `debian/control`
+ * [`efefc8b2`](https://gitlab.com/duplicity/duplicity/-/commit/efefc8b2):chg: Update doc cleanup pattern in `debian/rules`
+ * [`955713e7`](https://gitlab.com/duplicity/duplicity/-/commit/955713e7):chg: Update doc cleanup to remove `duplicity-*` files in `debian/rules`
+ * [`e8c0bc1a`](https://gitlab.com/duplicity/duplicity/-/commit/e8c0bc1a):chg: Add `get_data_files` for dynamic data file handling in `setup.py`
+ * [`137ae81d`](https://gitlab.com/duplicity/duplicity/-/commit/137ae81d):chg: Simplify doc handling by removing outdated duplicity docs
+ * [`f0fb534c`](https://gitlab.com/duplicity/duplicity/-/commit/f0fb534c):chg: Update dependencies, streamline configs, and refine CI
+ * [`6d719e1c`](https://gitlab.com/duplicity/duplicity/-/commit/6d719e1c):fix: Resolve PEP8 style issues and whitespace in backend and main modules
+
+rel.3.2.1.dev1 / 2026-08-15
+===========================
+
+ * [`29b7ca68`](https://gitlab.com/duplicity/duplicity/-/commit/29b7ca68):chg: Add `python3-gnupg` as a build dependency in `debian/control`
+ * [`d5ab54d3`](https://gitlab.com/duplicity/duplicity/-/commit/d5ab54d3):chg: Update doc cleanup pattern in `debian/rules`
+ * [`6fbffc54`](https://gitlab.com/duplicity/duplicity/-/commit/6fbffc54):chg: Update doc cleanup to remove `duplicity-*` files in `debian/rules`
+ * [`bf4b9c5d`](https://gitlab.com/duplicity/duplicity/-/commit/bf4b9c5d):chg: Add `get_data_files` for dynamic data file handling in `setup.py`
+ * [`c88e9239`](https://gitlab.com/duplicity/duplicity/-/commit/c88e9239):chg: Simplify doc handling by removing outdated duplicity docs
+ * [`e05cf2f2`](https://gitlab.com/duplicity/duplicity/-/commit/e05cf2f2):chg: Update dependencies, streamline configs, and refine CI
+ * [`3bced29a`](https://gitlab.com/duplicity/duplicity/-/commit/3bced29a):fix: Resolve PEP8 style issues and whitespace in backend and main modules
+
 rel.3.2.0 / 2026-08-10
 ======================
 

duplicity-3.2.1.dev2/PKG-INFO

@@ -0,0 +1,102 @@
+Metadata-Version: 2.4
+Name: duplicity
+Version: 3.2.1.dev2
+Summary: Encrypted backup using rsync algorithm
+Author-email: Kenneth Loafman <kenneth@loafman.com>
+Maintainer: Edgar Soldin, Thomas Laubrock
+Project-URL: Homepage, http://duplicity.us
+Project-URL: Download, https://gitlab.com/duplicity/duplicity/-/releases
+Project-URL: Issues, https://gitlab.com/duplicity/duplicity/-/issues
+Project-URL: Contact, https://lists.nongnu.org/mailman/listinfo/duplicity-talk
+Project-URL: Documentation, http://duplicity.us
+Project-URL: Repository, https://gitlab.com/duplicity/duplicity
+Project-URL: Changelog, https://gitlab.com/duplicity/duplicity/-/blob/main/CHANGELOG.md
+Classifier: Development Status :: 6 - Mature
+Classifier: Environment :: Console
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: C
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: System :: Archiving :: Backup
+Requires-Python: <3.15,>=3.10
+Description-Content-Type: text/markdown
+License-File: COPYING
+License-File: AUTHORS.md
+Requires-Dist: cryptography==43.0.3
+Requires-Dist: fasteners>=0.19
+Requires-Dist: httplib2
+Requires-Dist: pysocks
+Requires-Dist: python-gnupg
+Requires-Dist: requests
+Requires-Dist: requests-oauthlib
+Requires-Dist: azure-storage-blob
+Requires-Dist: b2sdk
+Requires-Dist: boto3
+Requires-Dist: botocore
+Requires-Dist: boxsdk[jwt]
+Requires-Dist: dropbox
+Requires-Dist: gdata-python3
+Requires-Dist: google-api-python-client
+Requires-Dist: google-auth-oauthlib
+Requires-Dist: jottalib
+Requires-Dist: mediafire
+Requires-Dist: megatools
+Requires-Dist: paramiko
+Requires-Dist: pexpect
+Requires-Dist: pydrive2
+Requires-Dist: pyrax
+Requires-Dist: python-swiftclient
+Dynamic: license-file
+
+# Duplicity
+
+Duplicity provides encrypted, bandwidth-efficient backups by producing encrypted tar-format volumes and uploading them to a remote or local file server. It uses the rsync algorithm for space-efficient incremental archives and GnuPG for security.
+
+## Key Features
+
+- **Encrypted & Signed**: Backups are safe from spying and modification using GnuPG.
+- **Bandwidth Efficient**: Only transmits changes since the last backup using the rsync algorithm.
+- **Incremental Archives**: Saves space by storing only the parts of files that have changed.
+- **Multiple Backends**: Supports a wide range of storage services (S3, Azure, B2, Google Drive, etc.) and protocols (SFTP, SCP, FTP, etc.).
+
+## Table of Contents
+
+- [Installation](README-INSTALL.md)
+- [Architecture](README-ARCH.md)
+- [Repository Access](README-REPO.md)
+- [Testing](README-TESTING.md)
+- [Logging](README-LOG.md)
+- [Release Process](README-RELEASE.md)
+- [Snap Support](README-SNAP.md)
+- [Development](#development)
+- [Help](#help)
+
+# DEVELOPMENT
+
+For more information on downloading duplicity's source code from the
+code repository and developing for duplicity, see [README-REPO](README-REPO.md).
+
+For source docs: https://duplicity.readthedocs.io/
+
+# HELP
+
+For more information see the duplicity web site at:
+
+  https://duplicity.us
+
+  or at:
+
+  https://duplicity.gitlab.io
+
+or post to the mailing list at:
+
+  https://lists.nongnu.org/mailman/listinfo/duplicity-talk
+
+or post a new issue at:
+
+  https://gitlab.com/duplicity/duplicity/-/issues

duplicity-3.2.1.dev2/README-ARCH.md

@@ -0,0 +1,62 @@
+# ARCHITECTURE
+
+```mermaid
+graph TD
+    subgraph Interface
+        Main["__main__.py (Entry Point)"]
+    end
+
+    subgraph Orchestration
+        DupMain["dup_main.py (Orchestration)"]
+    end
+
+    subgraph Support_Config ["Support & Config"]
+        CLI["cli_main.py (Argument Parsing)"]
+        Config["config.py (Global Settings)"]
+        LogUtil["log.py / util.py (Logging/Support)"]
+    end
+
+    subgraph Core_Logic ["Core Logic"]
+        Selection["selection.py (File Selection)"]
+        Backend["backend.py (Storage Layer)"]
+        Errors["errors.py (Exception Mgmt)"]
+    end
+
+    subgraph Operation
+        DiffDir["diffdir.py (Backup Logic)"]
+        Backends["backends/ (Storage Drivers)"]
+        PatchDir["patchdir.py (Restore Logic)"]
+    end
+
+    subgraph Engines_Metadata ["Engines & Metadata"]
+        LibRsync["librsync.py (rsync delta)"]
+        GPG["gpg.py (Encryption)"]
+        Manifest["manifest.py (Metadata)"]
+    end
+
+    Main --> DupMain
+    DupMain --> CLI
+    DupMain --> Config
+    DupMain --> LogUtil
+
+    CLI --> Selection
+    Config --> Backend
+    LogUtil ~~~ Errors
+    Errors -.-> LogUtil
+
+    Selection --> DiffDir
+    Backend --> Backends
+
+    DiffDir --> Backends
+    PatchDir --> Backends
+
+    DiffDir --> LibRsync
+    DiffDir --> GPG
+    DiffDir --> Manifest
+
+    PatchDir --> LibRsync
+    PatchDir --> GPG
+    PatchDir --> Manifest
+
+    Backends --> GPG
+```

duplicity-3.2.1.dev2/README-INSTALL.md

@@ -0,0 +1,159 @@
+# INSTALLATION
+
+Duplicity requires several system and Python dependencies. Choose one of the following methods to install them.
+
+## (1) Pipx Installation (Recommended)
+
+This method is recommended for most users. It uses `pipx` to install duplicity into an isolated virtual environment, avoiding conflicts with system packages.
+
+### (1a) System Requirements
+The following should be installed by `apt`, `yum`, etc., depending on your OS.
+```shell
+sudo apt-get update 
+sudo apt-get install -y \
+        build-essential \
+        intltool \
+        lftp \
+        librsync-dev \
+        libffi-dev \
+        libssl-dev \
+        openssl \
+        megatools \
+        par2 \
+        python3-dev \
+        python3-lxml \
+        python3-pip \
+        python3-venv \
+        python3 \
+        rclone \
+        rsync \
+        rdiff \
+        tzdata
+```
+
+### (1b) Install and Update Pipx
+It is necessary to upgrade packaging tools to avoid installation failures.
+```shell
+sudo python3 -m pip install --upgrade pip pipx
+sudo pipx --global ensurepath  # for all users
+pipx ensurepath                # for single user
+```
+
+### (1c) Uninstall Previous Versions
+If you have an existing duplicity not installed by `pipx`, you must uninstall it first:
+```shell
+which -a duplicity
+# Use apt, yum, snap, or other command to remove existing instances.
+```
+
+### (1d) Install Duplicity
+```shell
+# For all users
+sudo pipx --global install duplicity
+
+# For single user
+pipx install duplicity
+```
+*Note: Use `--suffix=version` to keep multiple versions (e.g., `duplicity-2.0`).*
+
+## (2) APT Only Installation (Production)
+
+Use this method if you are on a Debian-based system and want to install all runtime dependencies via `apt`, avoiding `pip` entirely.
+
+```shell
+sudo apt-get update 
+sudo apt-get install -y \
+        build-essential \
+        intltool \
+        lftp \
+        librsync-dev \
+        libffi-dev \
+        libssl-dev \
+        openssl \
+        megatools \
+        par2 \
+        python3-dev \
+        python3-lxml \
+        python3-pip \
+        python3-venv \
+        python3 \
+        rclone \
+        rsync \
+        rdiff \
+        tzdata \
+        python3-cryptography \
+        python3-fasteners \
+        python3-httplib2 \
+        python3-socks \
+        python3-gnupg \
+        python3-requests \
+        python3-requests-oauthlib \
+        python3-azure-storage-blob \
+        python3-b2sdk \
+        python3-boto3 \
+        python3-botocore \
+        python3-dropbox \
+        python3-googleapi \
+        python3-google-auth-oauthlib \
+        python3-paramiko \
+        python3-pexpect \
+        python3-pydrive2 \
+        python3-swiftclient
+```
+
+## (3) APT Only Installation (Development)
+
+Use this method for development or testing. It includes all runtime dependencies plus testing and documentation tools.
+
+```shell
+sudo apt-get update 
+sudo apt-get install -y \
+        build-essential \
+        intltool \
+        lftp \
+        librsync-dev \
+        libffi-dev \
+        libssl-dev \
+        openssl \
+        megatools \
+        par2 \
+        python3-dev \
+        python3-lxml \
+        python3-pip \
+        python3-venv \
+        python3 \
+        rclone \
+        rsync \
+        rdiff \
+        tzdata \
+        python3-cryptography \
+        python3-fasteners \
+        python3-httplib2 \
+        python3-socks \
+        python3-gnupg \
+        python3-requests \
+        python3-requests-oauthlib \
+        python3-azure-storage-blob \
+        python3-b2sdk \
+        python3-boto3 \
+        python3-botocore \
+        python3-dropbox \
+        python3-googleapi \
+        python3-google-auth-oauthlib \
+        python3-paramiko \
+        python3-pexpect \
+        python3-pydrive2 \
+        python3-swiftclient \
+        python3-setuptools \
+        python3-setuptools-gettext \
+        black \
+        python3-coverage \
+        python3-pycodestyle \
+        pylint \
+        python3-pytest \
+        python3-pytest-cov \
+        python3-pytest-timeout \
+        python3-pytest-xdist \
+        python3-myst-parser \
+        python3-sphinx
+```

duplicity-3.2.1.dev2/README-LOG.md

@@ -0,0 +1,33 @@
+# duplicity's Log Output
+
+Duplicity's log output is meant as a means of reporting status and information 
+back to the caller.  This makes the life of a frontend writer much easier.
+
+The format consists of a stream of stanzas, each starting with a keyword and 
+some arguments, an optional suggested user text (each line of which starts with 
+". ") and ending with an endline.  Like so:
+
+```
+KEYWORD 3\n  
+. Hello!  All work and now play make Jack a...\n  
+. dull boy.\n  
+\n  
+```
+
+You can get this output by specifying either *--log-fd* or *--log-file*.
+
+Currently, duplicity writes out status messages like WARNING or ERROR followed 
+by a message number.  Each message number uniquely identifies a particular 
+warning or error so the frontend can take special action.  For example, an ERROR 
+of 2 is a command line syntax error.  Each message type has its own namespace 
+(i.e. a WARNING of 2 means something different than an ERROR of 2).  A number 
+of 1 is a generic, non-unique number for messages without their own code.
+
+For a list of current numbers, see log.py
+
+## HINTS FOR CONSUMERS
+
+1. Ignore any extra arguments on the keyword line.
+2. Ignore any stanzas that have a keyword you don't recognize.
+3. Ignore any lines in a stanza that start with a character you don't know.
+

duplicity-3.2.1.dev2/README-RELEASE.md

@@ -0,0 +1,66 @@
+# RELEASE PROCESS
+
+## Duplicity rel Checklist
+
+1. merge dev into main
+2. get Crowdin updates
+    - run "make pot"
+    - commit "chg:pkg: Run po/update-pot."
+    - wait for Crowdin MR
+    - fix & merge Crowdin MR
+      - add chg:pkg: to title
+      - click 'squash commits' and 'delete branch'
+3. run "tools/release-prep \<version\>"
+4. push to origin/main
+5. run "git push alpha : --tags"
+6. run "git push mirror : --tags"
+7. Launchpad PPAs
+    - [Release PPA](https://code.launchpad.net/~duplicity-team/+recipe/duplicity-release-git)
+    - edit the "Recipe contents" at the bottom to update the version number
+8. Launchpad SNAPs
+    - [Release SNAP](https://launchpad.net/~duplicity-team/duplicity/+snap/duplicity-rel)
+    - double check the settings so nothing is automatic
+9. "request builds" on both PPAs and SNAPS
+10. release pip version
+    - if the last pipeline for `main` was skipped:
+      - set CI_PIPELINE_SOURCE to "push"
+      - run new pipeline for `main`
+    - run jobs `wheels-linux` and `wheels-macos` once done
+11. update web pages in duplicity.gitlab.io
+    - set new version and date in index.wml
+    - commit and push
+12. release to GitLab releases
+13. send email to talk and announce
+14. send backup tarballs to sourceforge.net
+15. merge main into dev
+16. set next version in dev, e.g. 3.2.1-->3.2.2.dev0
+17. check builds for Launchpad PPAs, SNAPs, and wheels
+
+## Duplicity dev Checklist
+
+1. run "tools/release-prep \<version\>"
+2. Launchpad PPAs
+    - [Develop PPA](https://code.launchpad.net/~duplicity-team/+recipe/duplicity-develop-git)
+    - edit the "Recipe contents" at the bottom to update the version number
+3. Launchpad SNAPs
+    - [Develop SNAP](https://launchpad.net/~duplicity-team/duplicity/+snap/duplicity-dev)
+    - double check the settings so nothing is automatic
+4. run "git push alpha : --tags"
+5. run "git push mirror : --tags"
+6. "request builds" on both PPAs and SNAPS
+7. release pip version
+   - if the last pipeline for `main` was skipped:
+     - set CI_PIPELINE_SOURCE to "push"
+     - run new pipeline for `main`
+   - run jobs `wheels-linux` and `wheels-macos` once done
+8. set next version in dev, e.g. 3.2.1-->3.2.2.dev0
+9. check builds for Launchpad PPAs, SNAPs, and wheels
+
+## Versioning
+
+ - We use [semantic versioning](https://semver.org/).
+ - Dev releases are numbered like `3.2.1.dev0`.
+ - Full releases are numbered like `3.2.1`.
+ - We use `git tag rel.3.2.1.dev0` to mark dev releases.
+ - We use `git tag rel.3.2.1` to mark full releases.
+ - We no longer use alpha, beta, or rc for releases.

{duplicity-3.2.1.dev0 → duplicity-3.2.1.dev2}/README-REPO.md

@@ -19,6 +19,6 @@ By the numbers:
 ```shell
     $ PYTHONPATH=$DUP_ROOT duplicity/__main__.py -V
 ```
-You should see something like "duplicity 3.0.0 May 16, 2024".
+You should see something like "duplicity 3.2.1.dev0 August 11, 2026".
 
 Use PYTHONPATH to set the path each time that you use the binaries.

duplicity-3.2.1.dev2/README-SNAP.md

@@ -0,0 +1,90 @@
+# Building
+
+Some instructions and hints for building duplicity snaps.
+
+
+## Prerequisites
+
+1. Must be in a git clone of duplicity
+2. Must have all requirements.txt modules available
+3. For remote build (non-amd64) you'll need access to Launchpad
+
+
+## Build Process 
+
+1. cd into clone root
+2. Run `tools/makesnap [arm64,amd64,armhf,ppc64el]`
+   1. run without args to build amd64 only locally
+   2. run with all args to build remotely on LP
+3. Run `tools/installsnap` to install to local machine
+4. Run `tools/testsnap` to run simple tests
+5. Run `tools/pushsnap` to push snap(s) to edge
+6. Sign on to [snapcraft.io](https://snapcraft.io/duplicity/releases) to promote snaps if needed
+
+
+## Notes
+
+1. Running 1 with all args is by far the easiest.
+2. Do not remove makesnap's `--destructive-mode`!
+   1. it'll try to use `Multipass` and fail miserably
+   2. if it should run, it'll interfere with other VMs
+   3. use a Ubuntu 22.04 VM or Docker image (core22)
+
+
+## Step-by-step instructions for Ubuntu 22.04
+
+Starting from a **default Ubuntu 22.04 Desktop installation**
+
+1. update and upgrade all packages (run as root or use `sudo`)
+```
+apt-get update
+apt-get -V upgrade
+```
+2. install needed software (run as root or use `sudo`)
+```
+apt-get install python3-setuptools python3-distutils git snapcraft gettext
+```
+3. install python pip
+```
+sudo apt-get install python3-pip
+```
+4. clone duplicity version to local file system (choose existing tag e.g. "rel.3.2.1.dev0")
+```
+git clone https://gitlab.com/duplicity/duplicity.git -b rel.3.2.1.dev0
+```
+5. change into local git clone folder
+```
+cd duplicity/
+```
+6. install needed python modules for duplicity (needed for local builds)
+```
+python3 -m pip install -r requirements.txt
+```
+7. setup git user/email (needed for snapcraft remote build)
+```
+git config --global user.email "your@email.com"
+git config --global user.name "Your Name"
+```
+8. run snap creation script (any non-amd64 target platform will trigger the remote-build)
+```
+tools/makesnap arm64,amd64,armhf,ppc64el
+```
+9. the above should result in several duplicity-*.snap files under `build/duplicity-<version>/`, as remote build at times results in truncated snap packages it is a good idea to quickly check if the squash-images are fine.
+```
+ls -l build/duplicity-3.2.1.dev0/*.snap
+# example output
+#-rw-rw-r-- 1 user user 145268736 Dec 14 06:39 build/duplicity-3.2.1.dev0/duplicity_3.2.1.dev0_amd64.snap
+#-rw-rw-r-- 1 user user 212455424 Dec 14 06:39 build/duplicity-3.2.1.dev0/duplicity_3.2.1.dev0_arm64.snap
+#-rw-rw-r-- 1 user user 208789504 Dec 14 06:38 build/duplicity-3.2.1.dev0/duplicity_3.2.1.dev0_armhf.snap
+#-rw-rw-r-- 1 user user 219574272 Dec 14 06:39 build/duplicity-3.2.1.dev0/duplicity_3.2.1.dev0_ppc64el.snap
+# unsquashfs will print an error in case the image is corrupted
+for f in build/duplicity-*/*.snap; do echo $f; unsquashfs -l "$f" > /dev/null; done
+```
+10. if all went well the snaps can be uploaded to snapcraft
+```
+# use the `tools/pushsnap` script NEEDS '~/.snaplogin'
+tools/pushsnap
+# or do it manually
+snapcraft login
+for f in build/duplicity-*/*.snap; do echo "$f"; snapcraft upload "$f" --release edge; done
+```

duplicity-3.2.1.dev2/README-TESTING.md

@@ -0,0 +1,36 @@
+# Testing duplicity
+
+## Introduction
+
+Duplicity's tests are code, unit, and functional tests contained in the /testing folder of the main repository.  
+There are containers for each version of Python that we actively support.
+
+## Running tests on your branch
+
+The recommended approach is to test duplicity using Docker, to ensure that you are running tests in a known-good
+environment. You can run tests on your branch as follows:
+
+1. Install Docker
+2. run `testing/docker/build-dupCI.sh` to build containers.  
+3. run `testing/docker/run-dupCI.sh` to start the containers.  
+
+Please test your branch using this method and ensure all tests pass before submitting a merge request.
+
+The decorator `@unittest.expectedFailure` can be used to commit a known-failing test case without breaking the test 
+suite, for example to exhibit the behaviour in a bug report before it has been fixed.
+
+## Manual testing and running individual tests
+
+1. Docker containers
+Even if you wish to run tests manually, we recommend that you do this inside the provided Docker container to ensure
+that you have a clean and reproducible environment with all required dependencies for executing these. Please follow
+the instructions above. For running a single test, set 
+`PYTEST_ARGS` either with an export like `export PYTEST_ARGS=testing/test_code.py` or a temporary setting like 
+`PYTEST_ARGS=testing/test_code.py testing/docker/run-dupCI.sh`.
+2. Use `pytest` locally if you want to test code on your machine. See 
+https://docs.pytest.org/en/stable/contents.html for complete instructions on using `pytest`.
+See _Dependencies for testing_ to setup your environment.
+
+## Dependencies for testing
+If you should prefer to execute the tests locally without using Docker, see [README-INSTALL.md](README-INSTALL.md) for 
+comprehensive `apt` commands to set up your environment (see "APT Only Installation (Development)").