deja-dup doesn't recognize encryption for existing backups

Bug #831969 reported by Stefan Kirrmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Undecided
Unassigned

Bug Description

deja-dup version: 19.90
duplicity version: 0.6.12

since deja-dup 19.4 duplicity doesn't check correctly for previous encrypted backups, if doing an incremental backup. deja-dup is always adding the argument --no-encryption to duplicity

Revision history for this message
Stefan Kirrmann (stefan-kirrmann) wrote :
Revision history for this message
Michael Terry (mterry) wrote :

Confirmed, though it works fine with recent releases of Duplicity.

Changed in deja-dup:
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

Versions of duplicity before 0.6.14 have a bug that prevents our current 'is the backup encrypted' logic from working, hence this bug.

Looking at fixing this, I was reminded that I've been considering bumping the required version of duplicity to 0.6.14 for the data corruption bugs fixed in it and 0.6.13 (bug 487720 and bug 613244).

So I've done that in trunk, thus "fixing" this bug. You're still on 0.6.12, what distro are you using?

Changed in deja-dup:
status: Confirmed → Fix Committed
Michael Terry (mterry)
Changed in deja-dup:
milestone: none → 19.91
Revision history for this message
Stefan Kirrmann (stefan-kirrmann) wrote :

I'm using Archlinux and the Archlinux duplicity package is already flagged as out of date.

Manually modified package for duplicity 0.6.15, installed it on my system and encryption is detected again.
Thanks.

Michael Terry (mterry)
Changed in deja-dup:
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.