This bug was fixed in the package ubuntu-release-upgrader - 1:25.04.7
---
ubuntu-release-upgrader (1:25.04.7) plucky; urgency=medium
[ Nick Rosbrook ]
* DistUpgrade: re-work how user environment is accessed
* DistUpgrade: fix handling when pkg in BaseMetaPkgs is not in cache
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083575
Title:
failed upgrade left apt sources on wrong release
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/481563
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083575
Title:
failed
Looking closer at the code, this is already supposed to be handled, but
there is a control flow mistake. The logs hint at this too:
2024-10-02 17:30:48,273 ERROR No 'ubuntu-minimal' available/downloadable after
sources.list rewrite+update
2024-10-02 17:30:48,273 ERROR 'ubuntu-minimal' was not in
Our options here are:
* Do not continue if ubuntu-minimal is not installed.
* Install ubuntu-minimal first before trying to upgrade
* Catch the KeyError
* Add a global catch-all that always tries to rollback.
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this
This is a funny instance where ubuntu-minimal isn't even installed, so
after upgrading the sources we don't see one, so we fail a step too
early with a crash instead of doing a clean rollback.
** Tags added: rls-nn-incoming
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Tri
