I think this has gotten even worse in duplicity. I believe this used to only affect full backups. But now it seems to affect incremental backups too.
I've attached a simple reproduction script. It basically just does:
PASSPHRASE=one duplicity full /tmp/testdir file://$DIR
PASSPHRASE=two duplicity /tmp/testdir file://$DIR
Although the second duplicity run complains about a bad password, it will still continue and make an incremental backup with a different passphrase than the full volumes.
Tested with duplicity 0.7.18.2.
I've worked around this behavior in deja-dup 39.1.
I think this has gotten even worse in duplicity. I believe this used to only affect full backups. But now it seems to affect incremental backups too.
I've attached a simple reproduction script. It basically just does:
PASSPHRASE=one duplicity full /tmp/testdir file://$DIR
PASSPHRASE=two duplicity /tmp/testdir file://$DIR
Although the second duplicity run complains about a bad password, it will still continue and make an incremental backup with a different passphrase than the full volumes.
Tested with duplicity 0.7.18.2.
I've worked around this behavior in deja-dup 39.1.