Setting --tmpdir on Synology fails

[hasko]

Installed duplicity 0.6.05 on a Synology disk station. Using --tmpdir option and alternatively TMPDIR environment var renders the following messages:

GnuPG passphrase:
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
No signatures found, switching to full backup.
Retype passphrase to confirm:
Cleanup of temporary directory /volume1/public/tmp/duplicity-AfRpy0-tempdir failed - this is probably a bug.
Traceback (most recent call last):
  File "/opt/bin/duplicity-2.6", line 1241, in <module>
    with_tempdir(main)
  File "/opt/bin/duplicity-2.6", line 1234, in with_tempdir
    fn()
  File "/opt/bin/duplicity-2.6", line 1212, in main
    full_backup(col_stats)
  File "/opt/bin/duplicity-2.6", line 417, in full_backup
    globals.backend)
  File "/opt/bin/duplicity-2.6", line 295, in write_multivol
    globals.gpg_profile, globals.volsize)
  File "/opt/lib/python2.6/site-packages/duplicity/gpg.py", line 278, in GPGWriteFile
    bytes_to_go = data_size - get_current_size()
  File "/opt/lib/python2.6/site-packages/duplicity/gpg.py", line 270, in get_current_size
    return os.stat(filename).st_size
OSError: [Errno 2] No such file or directory: '/volume1/public/tmp/duplicity-AfRpy0-tempdir/mktemp-ZlwWIw-2'

Is this me being stupid? The Synology acting up weird? A bug??

Python 2.6, OS: Synology DSM 2.2-0959, target file system Amazon S3. I'll happily send the longer log if necessary, i.e. if it's really an obscure bug.

[Kenneth Loafman (kenneth-loafman)]

This bug was fixed in version 0.6.07. The current version is 0.6.08b.

[Snuske (snuske)]

Actually, I am getting the exact same exception on two Synology DS210j. One is running python2.5 and the other python2.6. I've downloaded and compiled version 0.6.09 of duplicity. It may be due to the temp files never being created.

Whether I am using the --tempdir argument or not doesn't affect this problem. Thus, I don't believe this is related to the #459511 bug.

DiskStation> /opt/local/bin/duplicity --tempdir /opt/tmp testb/ file://testb2
GnuPG passphrase:
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
No signatures found, switching to full backup.
Retype passphrase to confirm:
Cleanup of temporary directory /opt/tmp/duplicity-WRIpTq-tempdir failed - this is probably a bug.
Traceback (most recent call last):
  File "/opt/local/bin/duplicity", line 1239, in <module>
    with_tempdir(main)
  File "/opt/local/bin/duplicity", line 1232, in with_tempdir
    fn()
  File "/opt/local/bin/duplicity", line 1210, in main
    full_backup(col_stats)
  File "/opt/local/bin/duplicity", line 416, in full_backup
    globals.backend)
  File "/opt/local/bin/duplicity", line 294, in write_multivol
    globals.gpg_profile, globals.volsize)
  File "/opt/local/lib/python2.6/site-packages/duplicity/gpg.py", line 275, in GPGWriteFile
    bytes_to_go = data_size - get_current_size()
  File "/opt/local/lib/python2.6/site-packages/duplicity/gpg.py", line 267, in get_current_size
    return os.stat(filename).st_size
OSError: [Errno 2] No such file or directory: '/opt/tmp/duplicity-WRIpTq-tempdir/mktemp-6V75NZ-2'

[Snuske (snuske)]

Well, turns out gpg was missing in both systems... I'd installed gpg2 with ipkg and duplicity didn't like that and created all these error messages about missing mktemp files. A bit confusing for someone new to duplicity.

If anything, a sanity check in duplicity of the existence of gpg and whether it's the correct version could be neat?