duplicity incorrectly thinks backups are uploaded with --asynchronous-upload and gdocs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
duplicity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When duplicity is used to back up to Google Drive with the gdocs:// URL scheme and --asynchronous-
The gdocs backend should instead report back, telling duplicity that the upload has failed and stopping the backup as this can lead to incomplete backup chains when the internet connection is later reconnected.
root@polaris:~# lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
root@polaris:~# apt-cache policy duplicity
duplicity:
Installed: 0.7.01-1ubuntu1
Candidate: 0.7.01-1ubuntu1
Version table:
*** 0.7.01-1ubuntu1 0
500 http://
100 /var/lib/
root@polaris:~# duply dir backup
=======
duplicity 0.7.01 (January 11, 2015)
Args: /usr/bin/duplicity --archive-dir /tmp/.duply/cache --name duply_dir --encrypt-key 01234567 --sign-key 01234567 --verbosity 5 --exclude-
Linux polaris 4.0.0-040000-
/usr/bin/python 2.7.9 (default, Apr 2 2015, 15:33:21)
[GCC 4.9.2]
=======
...
A dir/file_1
A dir/file_2
AsyncScheduler: scheduling task for asynchronous execution
Writing duplicity-
Attempt 2 failed. gaierror: [Errno -2] Name or service not known
Writing duplicity-
Attempt 3 failed. gaierror: [Errno -2] Name or service not known
Writing duplicity-
Attempt 4 failed. gaierror: [Errno -2] Name or service not known
Writing duplicity-
Processed volume 1361
Writing duplicity-
Attempt 1 failed. gaierror: [Errno -2] Name or service not known
A dir/file_3
A dir/file_4
...