TypeError with multi backend

Bug #1854554 reported by Tommy Nguyen on 2019-11-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

This is similar to https://bugs.launchpad.net/duplicity/+bug/1851727

duplicity 0.8.07
Python 3.7.5
Fedora 31
$ duplicity collection-status

My duplicity.json contains the following contents:

        "description": "second drive",
        "url": "file:///home/tom/second_drive/backup/"
        "description": "third drive",
        "url": "file:///home/tom/third_drive/backup/"

The command results in the following stacktrace:

Traceback (innermost last):
  File "/usr/bin/duplicity", line 101, in <module>
  File "/usr/bin/duplicity", line 87, in with_tempdir
  File "/usr/lib64/python3.7/site-packages/duplicity/dup_main.py", line 1539, in main
  File "/usr/lib64/python3.7/site-packages/duplicity/dup_main.py", line 1561, in do_backup
  File "/usr/lib64/python3.7/site-packages/duplicity/dup_collections.py", line 745, in set_values
    self.get_backup_chains(partials + backend_filename_list)
  File "/usr/lib64/python3.7/site-packages/duplicity/dup_collections.py", line 897, in get_backup_chains
  File "/usr/lib64/python3.7/site-packages/duplicity/dup_collections.py", line 889, in add_to_chains
    if chain.add_inc(set):
  File "/usr/lib64/python3.7/site-packages/duplicity/dup_collections.py", line 358, in add_inc
    incset.end_time > self.incset_list[-1]):
 TypeError: '>' not supported between instances of 'int' and 'BackupSet'

This looks like a typo. Changing line 358 to "incset.end_time > self.incset_list[-1].end_time" appears to fix the error.

description: updated
Changed in duplicity:
assignee: nobody → Kenneth Loafman (kenneth-loafman)
importance: Undecided → Medium
milestone: none → 0.8.09
status: New → In Progress
Changed in duplicity:
milestone: 0.8.09 → 0.8.08
Changed in duplicity:
status: In Progress → Fix Committed
assignee: Kenneth Loafman (kenneth-loafman) → nobody
Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers