[Bug 2091714] Re: packagekit noble update uninstallable on armhf, depends on libapt-pkg6.0t64 (>= 2.8.2) from proposed

[Andreas Hasenack]

For completeness, I also installed packagekit from noble-proposed on
amd64:

ubuntu at n-packagekit-amd64:~$ sudo apt install packagekit -t noble-proposed -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  gir1.2-packagekitglib-1.0 libpackagekit-glib2-18 packagekit-tools
The following packages will be upgraded:
  gir1.2-packagekitglib-1.0 libpackagekit-glib2-18 packagekit packagekit-tools
4 upgraded, 0 newly installed, 0 to remove and 69 not upgraded.
Need to get 608 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 libpackagekit-glib2-18 amd64 1.2.8-2ubuntu1.1 [120 kB]
Get:2 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 gir1.2-packagekitglib-1.0 amd64 1.2.8-2ubuntu1.1 [25.6 kB]
Get:3 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 packagekit-tools amd64 1.2.8-2ubuntu1.1 [28.2 kB]
Get:4 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 packagekit amd64 1.2.8-2ubuntu1.1 [434 kB]
Fetched 608 kB in 0s (3119 kB/s)    
(Reading database ... 35177 files and directories currently installed.)
Preparing to unpack .../libpackagekit-glib2-18_1.2.8-2ubuntu1.1_amd64.deb ...
Unpacking libpackagekit-glib2-18:amd64 (1.2.8-2ubuntu1.1) over (1.2.8-2ubuntu1) ...
Preparing to unpack .../gir1.2-packagekitglib-1.0_1.2.8-2ubuntu1.1_amd64.deb ...
Unpacking gir1.2-packagekitglib-1.0 (1.2.8-2ubuntu1.1) over (1.2.8-2ubuntu1) ...
Preparing to unpack .../packagekit-tools_1.2.8-2ubuntu1.1_amd64.deb ...
Unpacking packagekit-tools (1.2.8-2ubuntu1.1) over (1.2.8-2ubuntu1) ...
Preparing to unpack .../packagekit_1.2.8-2ubuntu1.1_amd64.deb ...
Unpacking packagekit (1.2.8-2ubuntu1.1) over (1.2.8-2ubuntu1) ...
Setting up libpackagekit-glib2-18:amd64 (1.2.8-2ubuntu1.1) ...
Setting up gir1.2-packagekitglib-1.0 (1.2.8-2ubuntu1.1) ...
Setting up packagekit (1.2.8-2ubuntu1.1) ...
Setting up packagekit-tools (1.2.8-2ubuntu1.1) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libc-bin (2.39-0ubuntu8.3) ...
ubuntu at n-packagekit-amd64:~$ apt-cache policy packagekit
packagekit:
  Installed: 1.2.8-2ubuntu1.1
  Candidate: 1.2.8-2ubuntu1.1
  Version table:
 *** 1.2.8-2ubuntu1.1 100
        100 http://br.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1.2.8-2ubuntu1 500
        500 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
     1.2.8-2build3 500
        500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/2091714

Title:
  packagekit noble update uninstallable on armhf, depends on libapt-
  pkg6.0t64 (>= 2.8.2) from proposed

Status in packagekit package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  The noble packagekit update[1] to fix LP: #2086773 picked up those
  dependencies on armhf due to t64 mangling changes in the C++ symbols,
  and is now uninstallable:

  ubuntu at n-armhf:~$ sudo apt install packagekit
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   packagekit : Depends: libapt-pkg6.0t64 (>= 2.8.2) but 2.7.14build2 is to be installed
  E: Unable to correct problems, you have held broken packages.

  The planned fix is to remove apt 2.8.2 from noble-proposed (done),
  rebuild packagekit (this bug), and release that.

  1. https://launchpad.net/ubuntu/+source/packagekit/1.2.8-2ubuntu1

  [ Test Plan ]

  On a noble armhf system, install packagekit from noble-proposed. It
  must not pull in other non-packagekit packages from noble-proposed.

  In addition to that, the noble excuses report[2] should be clean of
  errors and show no interdependencies preventing the release of
  packagekit.

  
  2. https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble/update_excuses.html#packagekit


  [ Where problems could occur ]

  This is a no-change rebuild. Like all SRUs, it's always built with the
  proposed pocket enabled, but this time the newer apt 2.8.2 is not
  there, so that dependency will not be picked up. That being said, the
  risk is the same that an unintended dependency from noble-proposed
  will be picked up, but the test plan specifically checks for that.

  [ Other Info ]

  This is fixing a regression introduced by the release of
  https://launchpad.net/bugs/2086773 to updates, where even though it
  was noticed that the excuses page was flagging packagekit to be
  depending on apt from proposed, it was incorrectly deemed irrelevant
  by me (@ahasenack) at the time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2091714/+subscriptions