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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1264619 Title: When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations Status in Ubuntu GNOME: Confirmed Status in “deja-dup” package in Ubuntu: Confirmed Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1264619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
