From deebee352a92b6959fd41c914bb3eedea22ea740 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Tue, 8 Apr 2014 20:50:02 +0100 Subject: Bugfix: excluded files stayed in new generation --- yarns/0030-basics.yarn | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'yarns/0030-basics.yarn') diff --git a/yarns/0030-basics.yarn b/yarns/0030-basics.yarn index 22ca0f1d..4bc8439b 100644 --- a/yarns/0030-basics.yarn +++ b/yarns/0030-basics.yarn @@ -247,6 +247,25 @@ Time to backup. AND user U restores their latest generation in repository R into X THEN L, restored to X, matches manifest M +Excluded, already backed up files, are not included in next generation +---------------------------------------------------------------------- + +Until Obnam version 1.7.4, but fixed after that, Obnam had a bug where +a file that was not excluded became excluded was not removed from new +backup generations. In other words, if file `foo` exists and is backed +up, and the user then makes a new backup with `--exclude=foo`, the new +backup generation still contains `foo`. This is clearly a bug. This +scenario verifies that the bug no longer exists, and prevents it from +recurring. + + SCENARIO new generation drops excluded, previously backed up files + GIVEN a file foo in L, with data + WHEN user U backs up directory L to repository R + GIVEN user U sets configuration exclude to foo + WHEN user U backs up directory L to repository R + AND user U restores their latest generation in repository R into X + THEN L, restored to X, is empty + Changing backup roots --------------------- -- cgit v1.2.1