Hi. On Sun, Mar 07, 2010 at 01:38:21PM +1000, Alexander Zangerl wrote: > > workaround: it's trivial to get duplicity to clean that area. > > duplicity cleanup --extra-clean --force .... > takes care of removing precisely this old, uninteresting stuff. >
Thanks for caring. However, are you sure --extra-clean is a real workaround ? Yes it improves the situation WRT cleanup command, but is no workaround to the fact that remove doesn't remove all of old backups... so, maybe the local cache won't grow at all times, but the distant backend in any case will... and I suspect some operations like collection-status don't care about --extra-clean, which only applies to cleanup. I would then suggest to set the severity to important again to make sure this is fixed before entering a stable release. Please read the whole of the thread on upstream ML that discusses the issue, in any case ;) Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
