[Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-07-15 Thread Matthias Klumpp
If you install PackageKit, you don't need the Aptdaemon compatibility layer anymore. So I assume this is not really a problem if installing PK removes the compat-layer package of Aptd. ** Changed in: packagekit (Ubuntu) Importance: Undecided = Low -- You received this bug notification

[Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-07-15 Thread dino99
The dependants have now changed; so closing that report. ** Changed in: packagekit (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175025 Title: conflict with

[Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-06-04 Thread Matthias Klumpp
** Changed in: packagekit (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175025 Title: conflict with python3-aptdaemon.pkcompat To manage notifications

[Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-06-04 Thread dino99
@ Sebastian, @Matthias the problem are: - exposed in the first 2 lines of that report : python-aptdaemon.pkcompat removed by the packagekit upgrade - it seems that now python3-aptdaemon.pkcompat should be used instead - but now try to install both packagekit python3-aptdaemon.pkcompat : one

[Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-05-02 Thread dino99
@Sebastian here with Saucy ( Raring too) both policykit aptdaemon are used. And the policykit dependants list is much longer then the aptdaemon one. So maybe you said that we are on the transition way (post #2) for a possible future design, but right now you seems missing something. -- You

Re: [Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-05-02 Thread Sebastian Heinlein
Am 2013-05-02 08:26, schrieb dino99: @Sebastian here with Saucy ( Raring too) both policykit aptdaemon are used. And the policykit dependants list is much longer then the aptdaemon one. So maybe you said that we are on the transition way (post #2) for a possible future design, but right

[Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-05-01 Thread Sebastian Heinlein
We are using aptdaemon as the default package manager service and not packagekitd as Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175025 Title: conflict with python3-aptdaemon.pkcompat

[Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-05-01 Thread Matthias Klumpp
Yup, what Sebastian said :) Maybe packagekit-tools is compatible with Aptdaemon, but I haven't checked it. (but maybe someone did and changed the dependencies?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1175025] Re: conflict with python3-aptdaemon.pkcompat

2013-04-30 Thread dino99
** Description changed: - That newest packagekit has removed python-aptdaemon.pkcompat (used by packagekit-system-interface). + That newest packagekit (which is a packagekit-tools dependency) has removed python-aptdaemon.pkcompat (used by packagekit-system-interface). Its also a recommend