[Touch-packages] [Bug 1540135] Re: Make this metapackage conflict with kaccounts-providers

2016-02-19 Thread Alberto Mardegan
Looks like we got a better solution. Please follow bug 1451728, I'm closing this one as we won't make the packages conflict. ** Changed in: account-plugins (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages

[Touch-packages] [Bug 1540135] Re: Make this metapackage conflict with kaccounts-providers

2016-02-17 Thread Martin Klapetek
On a third thought, I think I'll just have the files we ship renamed. The thing is, by requiring a special tag in the .provider, it makes things harder for everyone while this is only a problem on *buntu. If both KAccounts and UOA will show double Google accounts or whatever, I would put that as

[Touch-packages] [Bug 1540135] Re: Make this metapackage conflict with kaccounts-providers

2016-02-08 Thread Martin Klapetek
On a second thought, the filtering could just as well be done on top of libaccounts, in the actual account gui (uoa and kaccounts). There the filtering is a matter of simple code in QSortFilterProxyModel (we already have one there anyway). This way the KDE providers would never show up in uoa and

[Touch-packages] [Bug 1540135] Re: Make this metapackage conflict with kaccounts-providers

2016-02-08 Thread Martin Klapetek
> If there are some common files that can be shared between the two implementations, we could create an account-plugins-common package, which could be used by both. If the maintainers of kaccounts-providers think that this is the case, let them comment here. The problem with this is client keys an

[Touch-packages] [Bug 1540135] Re: Make this metapackage conflict with kaccounts-providers

2016-02-02 Thread Matthew Scheirer
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 desig

[Touch-packages] [Bug 1540135] Re: Make this metapackage conflict with kaccounts-providers

2016-02-02 Thread Alberto Mardegan
Hi Matthew, thanks for your bug report. I'm not very fond of the proposed solution, because it would mean that one cannot have a workstation with both KDE and Unity installed. And I guess it's not uncommon to have some households with a shared computer, where some family members use KDE and some

[Touch-packages] [Bug 1540135] Re: Make this metapackage conflict with kaccounts-providers

2016-01-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: account-plugins (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://