severity 682837 important
thanks
I think something needs to be done with duplicity. I was hoping this would
be fixed upstream, but it doesn't look like it will, so it might be a good
idea to put in a temporary Debian patch.
Attached is what I have to apply to make backups work after each package
update: disable the backup messages that break my backups.
I would argue that removing debug messages is better than some of our users
not getting their backups done (which could of course lead to data loss).
Cheers,
Francois
--
Francois Marier identi.ca/fmarier
http://fmarier.org twitter.com/fmarier
--- collections.py.original 2013-01-09 19:41:03.364632733 +1300
+++ /usr/share/pyshared/duplicity/collections.py 2013-01-11 19:24:38.064543356 +1300
@@ -804,15 +804,11 @@
"""
for set in sets:
if set.add_filename(filename):
- log.Debug(_("File %s is part of known set") % (filename,))
break
else:
- log.Debug(_("File %s is not part of a known set; creating new set") % (filename,))
new_set = BackupSet(self.backend)
if new_set.add_filename(filename):
sets.append(new_set)
- else:
- log.Debug(_("Ignoring file (rejected by backup set) '%s'") % filename)
map(add_to_sets, filename_list)
sets, incomplete_sets = self.get_sorted_sets(sets)
