Comment 4 for bug 953756

I get exactly the same error with 1.4.1-2. I notice, though, that on upgrading to Pangolin, packagekit ends up not being installed (and zeroinstall-injector recommends but does not install it).

Attempting to install packagekit yields this; the second problem is likely just a mirror glitch (mismatched release numbers) but I'm not sure about the python-aptdaemon.pkcompat and packagekit conflicts -- looks like Ubuntu at some point switches to "providing" PackageKit APIs using this APT Daemon?

I'm traveling until the end of the week and my Internet connection is rather spotty; I'll try and look into aptdaemon next week unless you get there first. Thanks!

The following NEW packages will be installed:
  gdebi-core{a} packagekit packagekit-backend-aptcc{a}
The following packages will be upgraded:
  libpackagekit-glib2-14
1 packages upgraded, 3 newly installed, 0 to remove and 139 not upgraded.
Need to get 578 kB/589 kB of archives. After unpacking 1,746 kB will be used.
The following packages have unmet dependencies:
  python-aptdaemon.pkcompat: Conflicts: packagekit but 0.7.2-4ubuntu2 is to be installed.
  libpackagekit-glib2-dev: Depends: libpackagekit-glib2-14 (= 0.7.2-4ubuntu1) but 0.7.2-4ubuntu2 is to be installed.