update-manager has the code everywhere, but starting from jammy, apt is already keeping back phased updates, so it should not be triggered anymore (just nobody removed the duplicated logic :D)
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2098140 Title: Breaks: phased-dep (<< phasing version) removes phased-dep Status in apt package in Ubuntu: Triaged Status in update-manager package in Ubuntu: New Status in update-manager source package in Focal: New Status in apt source package in Jammy: New Status in update-manager source package in Jammy: Won't Fix Status in apt source package in Noble: New Status in update-manager source package in Noble: Won't Fix Status in apt source package in Oracular: New Status in update-manager source package in Oracular: Won't Fix Status in apt source package in Plucky: Triaged Status in update-manager source package in Plucky: Won't Fix Bug description: [Impact] If two intertwined updates are being released, call them "breaks-phased-dep" and "phased-dep", version 2; both are installed in version 1; and "breaks-phased-dep" is available to install (e.g. fully phased), then `apt full-upgrade/dist-upgrade` will remove "phased-dep" to install "breaks-phased-dep". The expected behavior is that "breaks-phased-dep" is kept back as the new version of the dependency is not yet ready. [Test plan] Regression test suite, with the addition of new test: # Test case breaks-phased-dep: A released update breaks installed version of phased-dep insertinstalledpackage 'phased-dep' 'all' '1' insertinstalledpackage 'breaks-phased-dep' 'all' '1' insertpackage 'unstable-updates' 'breaks-phased-dep' 'all' '3' 'Breaks: phased-dep (<< 3)' insertpackage 'unstable-updates' 'phased-dep' 'all' '3' 'Phased-Update-Percentage: 0' setupaptarchive testsuccessequal "Reading package lists... Building dependency tree... Calculating upgrade... The following packages have been kept back: breaks-phased-dep 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded." aptget dist-upgrade [Where problems could occur] here be dragons [Details] This should also affect the original implementation in update-manager. Basically both implementations work by first calculating the full upgrade, and then reverting any upgrades to phased packages using MarkKeep. However; in case of a Breaks, the phased package at this point is marked "remove" and not "upgrade", so the keep back logic does not trigger. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2098140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
