[Bug 2058227] Re: Crash during upgrade from Mantic to Noble due to Python 3.12

[Munch]

I'm not sure what's blocking it either, I just know that I still can't
upgrade from Mantic and don't feel comfortable forcing it just in case
something is critically broken that isn't listed there. The confusion
around what is and isn't blocking the upgrade involving some bugs that
were listed as hard to recover from this time around has me erring on
the side of caution.

https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043 lists https://pad.lv/2058227 as the only blocker, but the fix for that was released despite its status there being listed as only committed.
Meanwhile https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890#heading--known-issues just says upgrades are not supported, does not elaborate, but lists https://pad.lv/2063221 as one example, which is also fixed. If there are other critical issues blocking the upgrade, they should be listed too so users don't inadvertently bork their systems assuming it was safe to upgrade because the listed bugs were fixed.

-- 
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/2058227

Title:
  Crash during upgrade from Mantic to Noble due to Python 3.12

Status in apt-xapian-index package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  Upgrading from Mantic to Noble often triggers a crash related to Python 3.12 compatibility:
  ```
  Traceback (most recent call last):
    File "/usr/sbin/update-apt-xapian-index", line 66, in <module>
      import axi.indexer
    File "/usr/lib/python3/dist-packages/axi/indexer.py", line 27, in <module>
      import imp
  ModuleNotFoundError: No module named 'imp'
  ```

  I guess that the crash happens when the indexer code is called while
  still being in the Mantic version, but the default Python3 package has
  already been upgraded to 3.12. However, that situation doesn't happen
  all the time, and the upgrade is sometimes able to complete without
  crash.

  For some reasons, I mostly (only?) see this on Kubuntu upgrades.

  Maybe that situation could also happen while upgrading from Jammy, but
  as the upgrade is currently broken due to some other issues, I haven't
  seen it yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/2058227/+subscriptions