duplicity-team team mailing list archive

[edso <question192331@xxxxxxxxxxxxxxxxxxxxx>]

Question #192331 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/192331

edso posted a new comment:
python3 will probably not help you as duplicity has not been adapted to
so far.

no i don't use other options.

setcurtime is executed in several places but most importantly once in duplicity:main
http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/view/head:/bin/duplicity#L1232
this should be enough to initialize the value

i don't think your mounted drive is a problem here.

just to be sure, could you please diff compare your dup_time.py with this one
http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/view/844/duplicity/dup_time.py 
we had a similar issue in 0.6.08

if you feel up to it you could start investigating where duplicity looses the value.
will try to reproduce it python 2.6.5 ...

ede/duply.net

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.