Orphaned signature files not removed on backend

Bug #815507 reported by chrispoole on 2011-07-24
This bug affects 9 people
Affects Status Importance Assigned to Milestone

Bug Description

Possibly a duplicate of #519948.

Two backup chains exist on remote.

Running remove-all-but-n-full 1 --force should remove all files associated with
the oldest chain, but signature files are left behind.

This affects signature files from full backups and incremental backups. For the
former, they're left behind on the remote host; for the latter, they're left
behind on both remote and local hosts.

cleanup --force --extra-clean does remove these files, but they should be
removed by remove commands anyway.

Mailing list: http://lists.nongnu.org/archive/html/duplicity-talk/2011-07/msg00057.html

Rene Rattur (renerattur) on 2012-07-12
security vulnerability: no → yes
visibility: public → private
visibility: private → public
security vulnerability: yes → no
iceflatline (iceflatline) wrote :

Confirming same problem. Commands in current test script (run every 15m) used in order as follows:

duplicity --full-if-older-than 60m --encrypt-key="<phrase>" /home/foo/local/ scp://foo@target/remote/

duplicity remove-all-but-n-full 4 --force --encrypt-key="<phrase>" scp://foo@target/remote/

duplicity cleanup --extra-clean --force --encrypt-key="<phrase>" scp://foo@target/remote/

Using FreeBSD 9.0-Release; duplicity v0.6.19_2 compiled from ports.

I believe this may be related to Bug #519948.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers