duplicity (3.0.6.3-1) unstable; urgency=medium

  this version changes the handling of remote manifests:
  since version 3.0.6 duplicity by default downloads and decrypts all
  remote manifests before backing anything up.

  this breaks any setup that uses asymmetric encryption 
  if the private key is not present when duplicity runs.
  (ie. --encrypt-key is set, --sign-key is not used.)

  (symptom: duplicity first tells you that
  "Local and Remote metadata are synchronized, no sync needed."
  and then immediatley fails with an "Error processing remote file"
  and "decryption failed: secret key not available")

  to restore functionality for this scenario you will need
  to use the new option --no-check-remote.

 -- Alexander Zangerl <az@debian.org>  Mon, 22 Dec 2025 15:14:57 +1000

duplicity (3.0.3.2-1) unstable; urgency=medium

  this build does not include any python libraries beyond the absolute
  minimum needed for typical backends. (the newest python build infrastructure
  seems to insist in packaging everything and the kitchen sink. i do not
  agree with that. a plain duplicity installation should not pull
  in 170+ fairly obese packages.)

  please consult requirements.txt for the required dependencies, should you
  want to use duplicity with optional backends (ie. backends other
  than file, imap, rsync, scp, sftp, we3bdav).

 -- Alexander Zangerl <az@debian.org>  Sun, 29 Dec 2024 21:42:18 +1000
