duplicity public-key-only incompatible with gnupg 2.0.11

Bug #402794 reported by Anthem
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned

Bug Description

Applies to duplicity 0.5.17 and 0.6.2 under Linux.

Scenario:
duplicity --encrypt-key 1E05E475 --sign-key 93E42BEB --archive-dir /duplicity-archive /backup file:///duplicity-repository/
Only the public key part of the encryption key is present, both public and private keys of a separate signature key are present.

While the initial full backup will work, the incremental backup will fail with a gpg error saying it cannot decrypt the manifest. The --archive-dir switch does not seem to have any effect.

Solution 1: Either downgrade to GnuPG 1.4.9, or

Solution 2: modify the following line in collections.py:
            if "secret key not available" in message.args[0]:
to
            if "No secret key" in message.args[0]:

(The construction of an appropriate else-if-construct is left as an exercise to someone with python programming experience :)

Changed in duplicity:
status: New → Fix Committed
milestone: none → 0.6.03
Changed in duplicity:
importance: Undecided → Medium
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.