error text when repository corrupt is misleading

[matt.wartell]

During a run of duplicity where the previous run had failed due to a key error, I repeatedly hit the line:

   assert dup_time.curtime != dup_time.prevtime, "time not moving forward at appropriate pace - system clock issues?"

when the fault was that "duplicity cleanup" needed to be run. I apologize for not having saved logs. This bug could either be considered a documentation bug or a call for more robust consistency checking of the repository.

$ duplicity --version
duplicity 0.6.08b
$ python --version
Python 2.6.5
$ uname -a
Linux tallguy.local 2.6.32-22-core2 #33 SMP Tue May 25 08:51:25 EDT 2010 i686 GNU/Linux
# Ubuntu lucid with very minor kernel option changes

This is not related to (and happened prior to https://bugs.launchpad.net/duplicity/+bug/591364)

[Jens Finkhäuser (finkhaeuser-consulting)]

Same error as 784098, but as far as I can tell the reason is very different.