duplicity shouldn't sync so much

Bug #1686643 reported by Martin Nowak
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned

Bug Description

Too many commands of duplicity first sync manifests and signatures to the local cache, even though they could just work with remote data.
Since signature files can become multiple GB, this is fairly annoying, e.g. when checking collection-status from a dev machine or before removing old backups.
Syncing should only be done when it's necessary, or alternatively there should be at least an option to skip syncing.

Tags: enhancement
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.