Traceback (most recent call last):
File "/usr/bin/duplicity", line 1494, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1488, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1337, in main
do_backup(action)
File "/usr/bin/duplicity", line 1366, in do_backup
sync_archive(decrypt)
File "/usr/bin/duplicity", line 1100, in sync_archive
remote_metafiles, ignored, rem_needpass = get_metafiles(remlist)
File "/usr/bin/duplicity", line 992, in get_metafiles
pr = file_naming.parse(fn)
File "/usr/lib/python2.7/dist-packages/duplicity/file_naming.py", line 391, in parse
pr = check_inc()
File "/usr/lib/python2.7/dist-packages/duplicity/file_naming.py", line 332, in check_inc
t2 = str2time((m1 or m2).group("end_time"), short)
File "/usr/lib/python2.7/dist-packages/duplicity/file_naming.py", line 281, in str2time
t = dup_time.genstrtotime(timestr.upper())
File "/usr/lib/python2.7/dist-packages/duplicity/dup_time.py", line 278, in genstrtotime
return override_curtime - intstringtoseconds(timestr)
File "/usr/lib/python2.7/dist-packages/duplicity/dup_time.py", line 190, in intstringtoseconds
error()
File "/usr/lib/python2.7/dist-packages/duplicity/dup_time.py", line 181, in error
raise TimeException(bad_interval_string % interval_string)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 8: ordinal not in range(128)
As far as I can tell, this bug has been present in a similar form since 2012. This is on a Ubuntu 14.04.4 LTS system.
Thanks for looking into this. Let me know if there's any other information I can find.
I also have this problem with duplicity 0.6.23:
Traceback (most recent call last): duplicity" , line 1494, in <module> tempdir( main) duplicity" , line 1488, in with_tempdir duplicity" , line 1337, in main backup( action) duplicity" , line 1366, in do_backup archive( decrypt) duplicity" , line 1100, in sync_archive metafiles, ignored, rem_needpass = get_metafiles( remlist) duplicity" , line 992, in get_metafiles parse(fn) python2. 7/dist- packages/ duplicity/ file_naming. py", line 391, in parse python2. 7/dist- packages/ duplicity/ file_naming. py", line 332, in check_inc "end_time" ), short) python2. 7/dist- packages/ duplicity/ file_naming. py", line 281, in str2time genstrtotime( timestr. upper() ) python2. 7/dist- packages/ duplicity/ dup_time. py", line 278, in genstrtotime nds(timestr) python2. 7/dist- packages/ duplicity/ dup_time. py", line 190, in intstringtoseconds python2. 7/dist- packages/ duplicity/ dup_time. py", line 181, in error bad_interval_ string % interval_string)
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
do_
File "/usr/bin/
sync_
File "/usr/bin/
remote_
File "/usr/bin/
pr = file_naming.
File "/usr/lib/
pr = check_inc()
File "/usr/lib/
t2 = str2time((m1 or m2).group(
File "/usr/lib/
t = dup_time.
File "/usr/lib/
return override_curtime - intstringtoseco
File "/usr/lib/
error()
File "/usr/lib/
raise TimeException(
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 8: ordinal not in range(128)
As far as I can tell, this bug has been present in a similar form since 2012. This is on a Ubuntu 14.04.4 LTS system.
Thanks for looking into this. Let me know if there's any other information I can find.