Alexander Zangerl <[email protected]> writes: > On Wed, 12 May 2010 05:53:15 +0200, Olivier Berger writes: >>Info: AssertionError: time not moving forward at >>appropriate pace - system clock issues? > > sorry, but this is not a bug in duplicity. > > as upstream (kenneth loafman) states authoritatively in > > http://permalink.gmane.org/gmane.comp.sysutils.backup.duplicity.general/3954 > this report indicates a time-related problem on your system, and > duplicity cannot and will not work in such a setup, full stop. > > one possible culprit that i can think of would be running ntpdate from a > cronjob instead of using ntpd. >
Hmmm... I think such definitive answers tend to be a bit too fast some times. As you may have noticed there are at least 3 people having the same problem of clock then (wouldn't be so much of a surprise in itseff either;). I'm thinking that the fact that it happens when duplicity tries to restart a previous failed backup may lead to more investigation of the code (yes it would be a bug) needed (and the fact that it used to work before, AFAICT). Anyway, leaving this closed on Debian matters not much, since it's known upstream, and search engines are aware now, should others have more hints to provide. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
