Comment 26 for bug 1770929

Hello,
in view of the above-mentioned post, it seems to me that the problem is not fully solved and therefore I will describe my findings. Today I tried to set up my small server backup to a second using duplicity package. I used some example for writing tiny script.

#!/bin/bash
export PASSPHRASE=some_pwd
export FTP_PASSWORD=some_ftp_pwd
duplicity ~/SQLBACKUP ftp://some_user@10.0.0.250/SQLBACKUP
unset PASSPHRASE
unset FTP_PASSWORD

When I ran the script, I got the errors listed above, but a directory SQLBACKUP was created on the target server. The permissions of this directory were okay (some similar bug), so I tried to run the script a second time and the backup went without errors. Other backups were already running without errors too. In my opinion, the problem may be that it fails to create a backup directory on the target server fast enough. As a target server I used ftp server on Windows once and second ftp server on Ubuntu 18.04 and the result was always the same (physically three machines on network: one with duplicity and two ftp servers). When I prepared SQLBACKUP directory on the target server manually, the backup went without errors too.

machine with duplicity:
-----------------------
Ubuntu 18.04.4 LTS
Python 2.7.17
duplicity 0.7.17 (from Ubuntu repository)
lftp version 4.8.1

Perhaps a small loop in the depths of duplicity package, that tests whether a directory has already been created, would help :-).