© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
I did some research to ensure that removing the Breaks is safe. Some of this repeats what we covered already but I'm stating it again so my logic is self-contained here.
If python-is-python2 is installed on Focal and I upgrade to Jammy, then python-is-python2 gets removed because of the Breaks.
If python-is-python2 is installed on Impish and I upgrade to Jammy using do-release-upgrade, then python-is-python2 remains but the installer offers to remove it as obsolete. I can refuse, however.
Therefore, by adjusting things so that in the upgrade from Focal to Jammy python-is-python2 can stay installed, I'm not changing behaviour from what the Impish to Jammy upgrade allows anyway. Note that the user will still need to state that they don't want to remove obsolete packages. This is the default if you just press Return.
On Jammy, python3-yaml (src:pyyaml) Breaks python (<< 2.7.18)
On Jammy, python3-six (src:six) Breaks python (<< 2.7.18)
On Focal, python-is-python2 Provides python (= 2.7.17-1)
On Impish, python-is-python2 Provides python (= 2.7.18-2)
Nothing else on Focal nor Impish Provides python.
python is not a concrete package on Focal nor Impish.
On both Focal and Impish, python-is-python2 Depends on python2 but has no Depends or Recommends on any other package.
Therefore the only impact of this change will be against the python-is-python2 package and I don't expect there to be unexpected interactions with any other package by removing the Breaks.