[Duplicity-talk] Problems with invalid characters in scp command

[Iwan Vosloo]

Hi there,

We've been using duplicity for quite some time without problems, but
recently it started complaining about "invalid characters in scp
command".  What triggered the problem is either our upgrade from ubuntu
dapper to edgy, or our changing of the timezone of the machine on which
duplicity runs.  I suspect the latter (see the filenames below).  The
timezone used to be GMT, we changed it to GMT+2 by setting the contents
of /etc/timezone to "Africa/Johannesburg".

I include the stack trace below... any ideas how we can fix this?

Thanks
-i
--------------------------------------------------------
invalid characters in scp command!
here:+02:00.to.2006-11-16T06:28:17+02:00.vol1.difftar.gpg
try using a wildcard to match this file/directory
lost connection
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 358, in ?
    if __name__ == "__main__": main()
  File "/usr/bin/duplicity", line 352, in main
    else: incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 162, in incremental_backup
    bytes_written = write_multivol("inc", tarblock_iter,
globals.backend)
  File "/usr/bin/duplicity", line 86, in write_multivol
    backend.put(tdp, dest_filename)
  File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line
277, in put
    self.run_command(commandline)
  File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line
143, in run_command
    raise BackendException("Error running '%s'" % commandline)
duplicity.backends.BackendException: Error running 'scp -o BatchMode=yes
-i /somefilewithsshkeys /tmp/tmp2q7GHU
address@hidden:backup/duplicity-inc.2006-11-13T08:32:36+02:00.to.2006-11-16T06:28:17+02:00.vol1.difftar.gpg'

signature.asc
Description: This is a digitally signed message part