[Duplicity-tracker] [bug #25308] Signatures orphaned if from another time zone

[anonymous]

URL:
  <http://savannah.nongnu.org/bugs/?25308>

                 Summary: Signatures orphaned if from another time zone
                 Project: duplicity
            Submitted by: None
            Submitted on: Tue 13 Jan 2009 09:47:51 PM UTC
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

I noticed when doing incremental backups that duplicity claimed that some
files were changed even though I had done many other incremental backups since
they were last modified. I tracked it down to the "if pr.start_time !=
self.end_time:" test failing in collections.py after a time zone change, which
made it ignore all signature files in the new time zone.

Reproduce it like this:

  mkdir tmp target && touch tmp/{foo,bar}
  TZ=UTC   PASSPHRASE=foo duplicity tmp/ file://target/
  TZ=UTC   PASSPHRASE=foo duplicity tmp/ file://target/
  TZ=UTC+1 PASSPHRASE=foo duplicity tmp/ file://target/
  TZ=UTC+1 PASSPHRASE=foo duplicity tmp/ file://target/

You will see an output like:

  Warning, discarding last backup set, because of missing signature file.
  Warning, found the following orphaned signature file:
 
duplicity-new-signatures.2009-01-13T20:43:10-01:00.to.2009-01-13T20:43:13-01:00.sigtar.gpg
  Warning, found incomplete backup sets, probably left from aborted session
  [...]

Tested with Duplicity 0.5.06 .





    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?25308>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/