Comment 14 for bug 1396611

Bringing the bug up to speed. It seems that Xenial is not getting package kit 1.0, so the 0.8 version that has a click backend can remain in Xenial and can be used. And it is in the Xenial archive. So we're all good as far as repositories are concerned. But it doesn't work by default.

This is related to the python3-aptdaemon.pkcompat getting installed, which makes aptdaemon act the PackageKit backend instead of PackageKit itself. You can fix an image by doing "apt install packagekit" which will cause it to be removed. Then PackageKit itself will handle the pkcon commands and install the package correctly.

So that is the first part of this bug, and results in a system that can install Click package correctly. We need to figure out which seeds/packages it makes sense to put the appropriate package dependencies in.

The second part is that by default on the desktop PackageKit is using PolicyKit for a privilege request. Unity8 doesn't currently have a PolicyKit handler. We'll need to add that to the system so that an appropriate prompt can be shown on install.