old signature files left around by remove-older-than
Bug #706885 reported by
Max Kanat-Alexander
This bug report is a duplicate of:
Bug #519948: remove-* commands don't remove signature-files.
Edit
Remove
This bug affects 13 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
New
|
Low
|
Unassigned |
Bug Description
duplicity 0.06.06
Python 2.4.3
CentOS 5
Running remove-older-than is leaving around the full-signatures
Here's the command I'm using:
duplicity remove-older-than 31D scp://<email address hidden>
I'll attach the entire log.
summary: |
- old full signature files left around by remove-older-than + old signature files left around by remove-older-than |
To post a comment you must log in.
i also see this behaviour with 0.6.08/11 and someone in the mailing list as well. see:
http:// thread. gmane.org/ gmane.comp. sysutils. backup. duplicity. general/ 4424
must be a bug in the cleaning code. Probably got introduced with the extra cleaning and keeping sigs for listing older backups.
in my case it keeps the files 'duplicity- full-signatures .*.sigtar. gpg' and 'duplicity- new-signatures. *.to.*. sigtar. gpg' .. seems to be all signatures to me (changed the subject accordingly)
ede/duply.net