Here's the test script I mentioned. It's a pared-down, consolidated version of a test I added to the test suite for Deja Dup. Run it like "python forever-test.py". It will pop up a bunch of dialogs that will fill themselves in. It will *not* change your existing Deja Dup preferences. It will try to backup your current directory a few times to a folder in /tmp, adjust the time stamps of the backups, and then backup some more.
On 14.1, you'll see the following after a bunch of spew and dialogs:
** (deja-dup:11694): DEBUG: DuplicityInstance.vala:552: duplicity (11709) exited with value 0
Traceback (most recent call last):
File "./delete", line 135, in run
success = method()
File "./delete", line 255, in forever
assert num_manifests() == 3 and num_manifests('full') == 3
AssertionError
FAILED
On 14.2, you'll see:
** (deja-dup:12621): DEBUG: DuplicityInstance.vala:552: duplicity (12631) exited with value 0
PASSED
I'm sorry I can't provide an easier way to test this fix. The problem is that the bug exposes itself after a period of a year. So I found it by using my test suite, of which this script is a bastardization.
Here's the test script I mentioned. It's a pared-down, consolidated version of a test I added to the test suite for Deja Dup. Run it like "python forever-test.py". It will pop up a bunch of dialogs that will fill themselves in. It will *not* change your existing Deja Dup preferences. It will try to backup your current directory a few times to a folder in /tmp, adjust the time stamps of the backups, and then backup some more.
On 14.1, you'll see the following after a bunch of spew and dialogs: ce.vala: 552: duplicity (11709) exited with value 0
** (deja-dup:11694): DEBUG: DuplicityInstan
Traceback (most recent call last): 'full') == 3
File "./delete", line 135, in run
success = method()
File "./delete", line 255, in forever
assert num_manifests() == 3 and num_manifests(
AssertionError
FAILED
On 14.2, you'll see: ce.vala: 552: duplicity (12631) exited with value 0
** (deja-dup:12621): DEBUG: DuplicityInstan
PASSED
I'm sorry I can't provide an easier way to test this fix. The problem is that the bug exposes itself after a period of a year. So I found it by using my test suite, of which this script is a bastardization.