Package: duplicity
Version: 0.6.08b-1+b1
Severity: important

I believe I had a connectivity problem which interrupted a transfer, and
since then duplicity has failed on every run saying:

"time not moving forward at appropriate pace - system clock issues?"
 - which was the result of a failed assertion.

I examined the surrounding code:

if dup_time.curtime == dup_time.prevtime:
        time.sleep(2)
        dup_time.setcurtime()
        assert dup_time.curtime != dup_time.prevtime

... this appears at first glance to get the current time, sleep for two
seconds, and then get the current time again, before comparing the two times.

.. however having modified the code to print the time stamps, and
subsequently investigating dupclicity's metadata, it would appear that
both pretime and curtime are set from the timestamp of a file, and thus
the test always fails.  To the best of my knowledge there are no system
clock issues on this system, and the error appears to be a duplicity bug.

The system has been running squeeze for a while, and duplicity was updated
from lenny-backports to squeeze during September (duplicity
 0.6.08b-1~bpo50+2 -> 0.6.08b-1+b1).


I have not investigated further, but see output below for the details of
the modified asssertion etc. etc.

A search of google would appear to show multiple people hitting the same
issue in the past.

HTH.

Thanks,

Tim.




zebedee:/home/tim# date ; /usr/local/bin/duplicity-backup.sh ; date
Sat Jan  8 23:20:09 GMT 2011
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? %s %s %s %s" % (`dup_time.curtime`, 
`dup_time.prevtime`, `dup_time.curtimestr`, `dup_time.prevtimestr`)
AssertionError: time not moving forward at appropriate pace - system clock 
issues? 1289355757L 1289355757L '20101110T022237Z' '20101110T022237Z'
Sat Jan  8 23:20:45 GMT 2011
zebedee:/home/tim# locate .part | grep duplicity | xargs ls -ald
-rw------- 1 root root      226 Nov 10 02:23 
/u2/duplicity-metadata/e8f0606cd67aab172093bd8ba7a2c52c/duplicity-inc.20101109T022237Z.to.20101110T022237Z.manifest.part
-rw------- 1 root root 14838272 Nov 10 02:23 
/u2/duplicity-metadata/e8f0606cd67aab172093bd8ba7a2c52c/duplicity-new-signatures.20101109T022237Z.to.20101110T022237Z.sigtar.part

zebedee:/home/tim# cat 
/u2/duplicity-metadata/e8f0606cd67aab172093bd8ba7a2c52c/duplicity-inc.20101109T022237Z.to.20101110T022237Z.manifest.part
Hostname zebedee.config
Localdir /
Volume 1:
    StartingPath   .  
    EndingPath     
home/tim/Maildir/.Archive.2010-Q1Q2/cur/1260875684.V904I2b541dM571720.zebedee:2,S
 4
    Hash SHA1 8f950fcdd93130acdcfaa5d36cb71cf59cc9851e


-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages duplicity depends on:
ii  gnupg                   1.4.10-4         GNU privacy guard - a free PGP rep
ii  libc6                   2.11.2-7         Embedded GNU C Library: Shared lib
ii  librsync1               0.9.7-7          rsync remote-delta algorithm libra
ii  python                  2.6.6-3+squeeze4 interactive high-level object-orie
ii  python-central          0.6.16+nmu1      register and build utility for Pyt
ii  python-pexpect          2.3-1            Python module for automating inter

duplicity recommends no packages.

Versions of packages duplicity suggests:
pn  ncftp                         <none>     (no description available)
ii  python-boto                   1.9b-4     Python interface to Amazon's Web S

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/duplicity (from duplicity package)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to