** Changed in: duplicity
Status: New => Invalid
--
You received this bug notification because you are a member of
duplicity-team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/815507
Title:
Orphaned signature files not removed on backend
Status in Duplicity:
Invalid
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/815507/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~duplicity-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~duplicity-team
More help : https://help.launchpad.net/ListHelp