desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #159843
[Bug 1540135] Re: Make this metapackage conflict with kaccounts-providers
The upstream solution does not actually work (it uses libaccounts-glib
envars to set alternative profile directories, but apparmor will deny
kaccounts access to those files, and would require permissions
modifications in the Debian packages) and it breaks accounts-sso
intended use (because by design, you should be placing accounts in
/usr/share/accounts from multiple provider packages, which in theory
could be third party).
The problem with trying to make an upstream unfiied package is that
accounts-sso is seeing very little development and is effectively in
maintenance mode.
Having these packages conflict actually does not break either KDE's
Telepathy or Ubuntu's Empathy - the KDE client will still load Ubuntu
providers, and vice versa. The problem is they provide the same files,
and thus should conflict regardless.
You could be more selective and just make account-plugin-google and
account-plugin-twitter conflict for now, because then regardless of
which packages you have installed google and twitter signon
functionality would work. The KDE package however is not just those
provider files - it also includes GUI dialogs for owncloud and generic
services enablement. But then the problem becomes as KTP adds more
services to its online accounts you get additional conflicts.
I pinged Martin over at KDE to comment here about the viability of that
proposal.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1540135
Title:
Make this metapackage conflict with kaccounts-providers
Status in account-plugins package in Ubuntu:
Incomplete
Bug description:
Anyone that tries to install Kubuntu-meta, or from Kubuntu tries to
install Ubuntu-desktop, will hit conflicts with accounts-sso providers
in /usr/share/accounts/providers (and possibly in service files in the
future). As a result, many automatic bugs are being generated on both
packages relating to this conflict in both directions, below are the
most popular ones for each:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1539988
https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1489507
kaccounts-providers is imported from Debian directly without
repackaging and Debian does not package the Ubuntu account-plugins
anywhere. Upstream KDE is being forced to break accounts-sso standards
and impose systemwide envvars to work around that this package should
conflict with KDE's: https://bugs.kde.org/show_bug.cgi?id=347219
Either Ubuntu / Kubuntu should be amending the Debian package to make
it conflict with these plugin packages when importing it, or the
psmteam should make this package conflict with kaccounts-providers.
The later would be less work, since account-plugins is only packaged
in Ubuntu for Unity.
This change is necessary in Wily and beyond since those are the
releases shipping kaccounts-providers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1540135/+subscriptions
References