If I am not mistaken, Disco/19.04 doesn't have the fix backported yet: https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeController.py?h=ubuntu/disco-updates#n362 binaries_and_dirnames = [("python", "python"), ("python2", "python"), ("python3", "python3")]
While 19.10 does: https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeController.py?h=ubuntu/eoan#n362 binaries_and_dirnames = [("python3", "python3")] wolfgang-rumpf, * do you have python2 installed by any chance? * does /usr/bin/python point to /usr/bin/python2.7 or /etc/alternatives/python? * if it points to /etc/alternatives/python you are hitting the original bug I filed about the incorrect check performed by the release upgrader. Without the fix, it looks at /usr/bin/python while it only actually cares about python3. So if you fix this symlink everything will work as expected. If you just need to do it quickly on one system (i.e. upgrade your laptop): sudo rm /usr/bin/python sudo ln -s /usr/bin/python2.7 /usr/bin/python do-release-upgrade Also, do you remember why an alternative was set up in the first place? It would be helpful to understand where this kind of setup is coming from. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825655 Title: do-release-upgrade fails with "Your python3 install is corrupted" if /usr/bin/python points to /etc/alternatives/python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1825655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
