Public bug reported:

I've just spent an hour trying to understand why duplicity was not
deleting certain backup chains in "remove_all_inc_of_but_n_full" mode,
despite say it was. On every run, with the same parameters, it would
spit out:

Last full backup date: Tue Sep  9 16:47:20 2014
Deleting backup chains at times:
Tue Jul 29 05:40:01 2014
Wed Aug  6 05:40:01 2014
Deleting incremental signature chain Wed Aug  6 05:40:01 2014
Deleting incremental signature chain Wed Aug  6 05:40:01 2014
Deleting incremental signature chain Tue Jul 29 05:40:01 2014
Deleting incremental signature chain Tue Jul 29 05:40:01 2014
Deleting incremental backup chain Wed Aug  6 05:40:01 2014
Deleting incremental backup chain Tue Jul 29 05:40:01 2014

It turns out that those are full backups, and that duplicity _would_
have deleted any incremental chains attached to them (and probably has
on some previous run.) The attached patch is my suggested rewording of
the log message.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: duplicity 0.6.23-1ubuntu4.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 14 11:17:02 2014
InstallationDate: Installed on 2014-04-20 (147 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: duplicity (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug trusty

** Patch added: "More accurate log message in remove_all_inc_of_but_n_full mode"
   
https://bugs.launchpad.net/bugs/1369243/+attachment/4203560/+files/duplicity.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1369243

Title:
  Confusing log message in remove_all_inc_of_but_n_full mode

Status in “duplicity” package in Ubuntu:
  New

Bug description:
  I've just spent an hour trying to understand why duplicity was not
  deleting certain backup chains in "remove_all_inc_of_but_n_full" mode,
  despite say it was. On every run, with the same parameters, it would
  spit out:

  Last full backup date: Tue Sep  9 16:47:20 2014
  Deleting backup chains at times:
  Tue Jul 29 05:40:01 2014
  Wed Aug  6 05:40:01 2014
  Deleting incremental signature chain Wed Aug  6 05:40:01 2014
  Deleting incremental signature chain Wed Aug  6 05:40:01 2014
  Deleting incremental signature chain Tue Jul 29 05:40:01 2014
  Deleting incremental signature chain Tue Jul 29 05:40:01 2014
  Deleting incremental backup chain Wed Aug  6 05:40:01 2014
  Deleting incremental backup chain Tue Jul 29 05:40:01 2014

  It turns out that those are full backups, and that duplicity _would_
  have deleted any incremental chains attached to them (and probably has
  on some previous run.) The attached patch is my suggested rewording of
  the log message.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: duplicity 0.6.23-1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 14 11:17:02 2014
  InstallationDate: Installed on 2014-04-20 (147 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1369243/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to