Setting --tmpdir on Synology fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Invalid
|
Undecided
|
Unassigned |
Bug Description
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/
Traceback (most recent call last):
File "/opt/bin/
with_
File "/opt/bin/
fn()
File "/opt/bin/
full_
File "/opt/bin/
globals.
File "/opt/bin/
globals.
File "/opt/lib/
bytes_to_go = data_size - get_current_size()
File "/opt/lib/
return os.stat(
OSError: [Errno 2] No such file or directory: '/volume1/
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.
This bug was fixed in version 0.6.07. The current version is 0.6.08b.