Hi. On Mon, Jul 06, 2009 at 07:05:20PM +0200, martin f krafft wrote: > > The duplicity handler could use the --archive-dir option, which > would make it run faster as it can use a local set of signatures to > determine which files have changed. >
I think that since duplicity 0.6.01, the archive dir use is now by default. Excerpt from its upstream changelog : New in v0.6.01 (2009/07/01) --------------------------- [SNIP] * The archive_dir (cache) is now stored in a standard location, defaulting to ~/.cache/duplicity. See http://standards.freedesktop.org/basedir-spec/latest/ [SNIP] * duplicity will now copy needed metadata from the remote store to the local cache as needed. This means that the first use after upgraded from 0.5.x will have the metadata copied to the local archive dir in order to sync both. ----------- So I believe the addition of this dir is now useless for regular duplicity runs (given that testing has duplicity 0.6.06), i.e. with its cache in /root/.cache/duplicity. If the goal is to be able to use another dir, then this ticket is still valid. Hope this helps. -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
