--gpg-options "--batch" fails with --full-if-older-than

Bug #1861519 reported by ñull on 2020-01-31

This bug report will be marked for expiration in 39 days if no further activity occurs. (find out why)

This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I use an encryption key without password and use "--gpg-options '--batch' " succesfully to avoid that my backup script hangs for that gpg key password that is still asked.

This works okay with the default incremental backups, but when I use it with "--full-if-older-than 1W" then it still asks the password as if the gpg batch option was never passed. Result is that my backup script fails weekly.

Could this be verified and fixed? Or is this already done so since duplicity 0.7.06?

Version 0.7.06 is ancient. We're now on 0.8.10. Please upgrade to the current version. This will assure that any bugs fixed since your release are available and may fix your issue.

There are multiple options both stable and daily:

* Stable tarball install - https://launchpad.net/duplicity/+download
* Daily duplicity builds - https://launchpad.net/~duplicity-team/+archive/ubuntu/daily-dev-trunk
* Stable snap builds - “sudo snap install duplicity —classic"
* Latest snap builds - “sudo snap install duplicity —classic —edge"
* Lates pip builds - “sudo pip install duplicity"

NOTE: UNinstall duplicity first if it was installed via the distribution repository.
      For Ubuntu that would be "sudo apt-get purge duplicity".

Changed in duplicity:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers