--extra-clean makes old backups unrestorable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
cleanup --extra-clean removes old backup chains' signature files, which i'd argue is dangerous:
- it makes those older chains unrestorable. the claim in the manpage about signatures not being needed
for restoration is a bit unhelpful, as restore silently ignores a --time pointing to such a chain and simply
restores from the oldest chain with signatures.
- those unusable chains still show up in collection-status, which is quite confusing
- cleanup with --extra-clean performs removal-related operations that should be handled by remove-*
and not cleanup.
the not-overly-
debian bug #724594.
i'd suggest that either the manpage be amended with a bit more warning about extra-clean (see attached patch),
or that extra-clean be removed altogether.
regards,
az
Changed in duplicity: | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
milestone: | none → 0.7.01 |
Changed in duplicity: | |
milestone: | 0.7.01 → 0.7.02 |
Changed in duplicity: | |
milestone: | 0.7.02 → none |
Changed in duplicity: | |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
Changed in duplicity: | |
assignee: | nobody → Kenneth Loafman (kenneth-loafman) |
milestone: | none → 0.8.11 |
Changed in duplicity: | |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
status: | Fix Committed → Fix Released |
az,
your assessment reads that old chains are unrestorable.
1. is this still valid to your knowledge?
2. if so, does it make a difference if --file-to-restore is given?
..ede/duply.net