@sil2100 The regression in time is back to the old behavior prior to
24.04.20; actually it's a bit faster as there is just a single action
group now. But the reason for it was that we iterated over all packages
in the cache and recorded their selected state in case we needed to undo
a change (verifying the change is allowed was equally expensive).

What triggers this? The run time is linear to the number of obsolete
Ubuntu packages (packages no longer in noble) you have installed. In a
small lxd VM, it is sub-second vs 20 seconds or so, on a desktop with
many obsolete packages installed it will be a lot longer.

Updates from jammy to noble won't see the regression, the apt 2.4.13 SRU
I just verified fixes the APT algorithm so it should never fallback.

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

Title:
  Upgrading from jammy to noble results in a linux-headers package being
  in a broken state

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to