[Bug 2061175] Re: Handle (t64) package replacements
Steve Langasek
2061175 at bugs.launchpad.net
Fri Apr 12 20:44:06 UTC 2024
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Critical
Assignee: Nick Rosbrook (enr0n)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/2061175
Title:
Handle (t64) package replacements
Status in ubuntu-release-upgrader package in Ubuntu:
Triaged
Status in ubuntu-release-upgrader source package in Noble:
Triaged
Bug description:
We should do something like:
for package in cache:
if package.is_installed and <candidate version is obsolete>:
replacement = <find a package in the archive that Conflicts/Breaks + Replaces + Provides it>
replacement.mark_install(auto_fix=False, auto_inst=False)
replacement.mark_remove(auto_fix=False)
To hint the solver to remove the installed pre-t64 packages and
install packages replacing it. We gotta do some auto_fix, auto_inst
False stuff as we do not want to resolve the dependencies at this
point, let the upgrader work on this.
I do not believe we have to protect our choice to remove the packages
here like we did for gpg-wks-server as the packages are not updatable,
but I can't say I've checked. Potentially maybe just the mark_install
are enough since they will inevitably result in removals anyway, but
this would be easier if the removal sticks around.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2061175/+subscriptions
More information about the foundations-bugs
mailing list