registry team mailing list archive

[Dirk Leinenbach <launchpad@xxxxxxxxxxxxxxxxx>]

Hi Moritz,

I got the same duplicity error message (I'm using duplicity directly not
via deja-dup):

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1251, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1244, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1226, in main
    incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 474, in incremental_backup
    assert dup_time.curtime != dup_time.prevtime, "time not moving forward at
appropriate pace - system clock issues?"
AssertionError: time not moving forward at appropriate pace - system clock
issues?
Local and Remote metadata are synchronized, no sync needed.

It turned out that the problem was caused by two .part files in
duplicities local archive:

duplicity-inc.20100501T230102Z.to.20100502T230102Z.manifest.part
duplicity-new-signatures.20100501T230102Z.to.20100502T230102Z.sigtar.part

deleting these files solved the problem for me

-- 
Unknown error while uploading duplicity-full-signatures
https://bugs.launchpad.net/bugs/502609
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.