Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Invalid
|
Undecided
|
Unassigned | ||
deja-dup (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I am currently testing out Ubuntu 17.10 and I noticed that Deja Dup (version 36.1-0ubuntu1) no longer supports S3 backups. I have already installed the packages python-boto python-cloudfiles but the "Amazon S3" option is missing from the Storage location tab.
Using dconfig editor, I can see the S3 records created under /org/gnome/
lsb_release -d
Description: Ubuntu Artful Aardvark (development branch)
dpkg-query -W deja-dup duplicity
deja-dup 36.1-0ubuntu1
duplicity
gsettings list-recursively org.gnome.DejaDup
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic false
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'remote'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check '2017-10-
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
summary: |
- Amazon S3 stora location missing from Deja Dup 36.1-0ubuntu1 + Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1 |
tags: | added: artful |
I assume your testing was on a fresh system, not an upgrade?
We have intentionally hidden several cloud providers by default. See this wiki page for the explanation and how to unhide them: /wiki.gnome. org/Apps/ DejaDup/ Clouds
https:/
But on upgrades, your old settings shouldn’t be affected. If that’s the case, this is a new bug. Otherwise, I’ll mark this bug closed as intentional behavior.
(You also shouldn’t have to manually install python-boto and such anymore. If you have S3 set up in deja-dup, we’ll prompt you to install what we need now.)