Re: [Duplicity-talk] AssertionError: time not moving forward

[edgar . soldin]

you should check the distros software tool (apt,yast) just to be sure...

$PYTHONPATH or /usr/lib/python* , you can find a folder named duplicity (that's 
the libraries)
remove the above and the binaries (duplicity, rdiffdir) somewhere in /bin
there are also manpage and other datafiles, but that should not break the new 
duplicity if they are leftover.

..ede/duply.net


On 01.06.2011 11:09, Andre Schütz wrote:
> Hello,
> 
> I do not know how the system was installed.
> This was done by my predecessor who configured
> the system and installed duplicity.
> 
> I found the duplicity-0.6.08b.tar.gz. I think it
> was installed from the tar.gz.
> 
> Andre
> 
> On Wed, 01 Jun 2011 09:35:12 +0200
> address@hidden wrote:
> 
>> depends on the way you installed it tar.gz or from distro?
>>
>> ede/duply.net
>>
>> On 01.06.2011 09:33, Andre Schütz wrote:
>>> Thanks for the fast reply,
>>>
>>> I will try the new version and report the results.
>>>
>>> Is there a description how to uninstall the current duplicity
>>> version?
>>>
>>> Thanks,
>>> Andre
>>>
>>> sudo apt-
>>>
>>> On Tue, 31 May 2011 14:30:00 +0200
>>> address@hidden wrote:
>>>
>>>> Please try 0.6.13. Changelog states
>>>>
>>>> http://duplicity.nongnu.org/CHANGELOG
>>>> Bugs closed in this release:
>>>> 579958     Assertion error "time not moving forward at appropriate pace"
>>>>
>>>> Uninstall the distros duplicity first and then
>>>>
>>>> # install needed packages first
>>>> python python-devel librsync-devel
>>>> # download & extract
>>>> wget http://.../duplicity-0.6.07.tar.gz
>>>> tar xvf duplicity-0.6.07.tar.gz
>>>> cd duplicity-0.6.07/
>>>> # install into PREFIX
>>>> python setup.py install
>>>>
>>>> except it's not 0.6.07 in your case .. good luck ede/duply.net
>>>>
>>>>
>>>> On 31.05.2011 14:26, Andre Schütz wrote:
>>>>> Hello,
>>>>>
>>>>> we are using duplicity for our incremental backup and since a few days, 
>>>>> we get the following error:
>>>>>
>>>>> Error:
>>>>> =======================================================
>>>>>
>>>>> Local and Remote metadata are synchronized, no sync needed.
>>>>> Last inc backup left a partial set, restarting.
>>>>> Last full backup date: Sun Nov  7 01:00:01 2010
>>>>> Traceback (most recent call last):
>>>>>   File "/usr/bin/duplicity", line 1239, in <module>
>>>>>     with_tempdir(main)
>>>>>   File "/usr/bin/duplicity", line 1232, in with_tempdir
>>>>>     fn()
>>>>>   File "/usr/bin/duplicity", line 1214, 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?
>>>>>
>>>>> We use the following configuration:
>>>>>
>>>>> duplicity: Version 0.6.08b released March 11, 2010
>>>>> Operating System: Ubuntu 8.04.4 hardy
>>>>>
>>>>> The backup is stored in a Rackspace Cloud Files Container.
>>>>>
>>>>> We found another solution that described a similar error. The solution 
>>>>> was to delete the 
>>>>> .part files in the /root/.cache/duplicity local folder. We renamed the 
>>>>> .part files but the
>>>>> error was not fixed.
>>>>>
>>>>> Does anybody have an idea how to solve that problem?
>>>>>
>>>>> Many thanks,
>>>>> Andre Schütz
>>>>>
>>>>> _______________________________________________
>>>>> Duplicity-talk mailing list
>>>>> address@hidden
>>>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>>>
>>>> _______________________________________________
>>>> Duplicity-talk mailing list
>>>> address@hidden
>>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>>
>>>
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
>