When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations

[Phil Wyett]

When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: deja-dup 29.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Dec 28 03:23:12 2013
InstallationDate: Installed on 2013-12-28 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131227)
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Vasil Yakauleu (vasilbelarus)]

I can reproduce this issue in Ubuntu-GNOME 14.04 (latest updates) i.e. still can see "s3" and "cloudfiles" in the list of locations to store files after packages have been deleted(and system restarted)

[Alberto Salvia Novella (es20490446e)]

Priority set to "Medium" because the bug has a moderate impact on a core package.

[Michael Terry (mterry)]

Here's why this happens btw. The backend packages are just meta packages right now that install the needed dependencies for the various backends. Deja Dup itself looks directly for the dependencies.

Personally, as both upstream maintainer and Ubuntu packager, I don't think this is a big deal, since the backends still work (i.e. the UI isn't showing you something broken). But I understand why this might not be what you expect.

[Michael Terry (mterry)]

This situation is better in artful now. If a backend is missing packages it needs, it will prompt to install them. And we no longer use the meta packages that caused the confusion here.