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
the issues in Comment #10 appear to be closed, and they are not mentioned
anyway on
https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043
so it is confusing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So, what you are saying is that https://discourse.ubuntu.com/t/noble-
numbat-24-04-release-status-tracking/44043 needs an update, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058227
Title:
In reply to Comment #10
Apparently not. According to release notes [1], there are more critical
bugs blocking the Mantic to Noble upgrades. This include the libglib
transitional package with Y2038 handling [2] and Thunderbird DEB-to-Snap
conversion [3]
[1]:
It's just that this bug is listed as the only blocker on the Release
Status Tracking page:
https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-
tracking/44043#current-blockers-for-enabling-upgrades-from-mantic-6
--
You received this bug notification because you are a member of
Yes, sorry, I got confused, upgrades from Mantic are still hidden behind the
`-d` flag. That means you need `do-release-upgrade -d` to get it.
Be advised though that if it's not enabled yet, there might be remaining issues
that I'm not aware of, even if from my point of view, the jump from
That is weird, when I try release upgrade it shows the following. Its a
```
$ sudo do-release-upgrade -m desktop
Checking for a new Ubuntu release
No new release found.
```
I am on Mantic right now
```
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 23.10"
NAME="Ubuntu"
VERSION_ID="23.10"
A quirk has been added to ubuntu-release-upgrader so this issue doesn't
appear anymore, and upgrades from Mantic to Noble are already enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058227
When can we expect this change to unblock upgrade from Mantis to Noble.
https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-
tracking/44043
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: apt-xapian-index (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058227
Title:
Crash during upgrade from Mantic to Noble due to Python 3.12
This bug was fixed in the package ubuntu-release-upgrader - 1:24.04.14
---
ubuntu-release-upgrader (1:24.04.14) noble; urgency=medium
[ Brian Murray ]
* Set prompt to lts because 24.04 is one (LP: #2061214)
[ Nick Rosbrook ]
* DistUpgradeQuirks: tell apport to ignore
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/464340
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058227
Title:
Crash
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058227
Title:
Crash during upgrade from Mantic to Noble due to
From what I can recall of the meeting there was a more general idea of
stopping all systemd user services and cronjobs tha could fall over
during a distribution upgrade. For this specific problem we can either
stop running update-apt-xapian-index or just suppress the crashes.
--
You received
From what I can tell, there is not a systemd service or anything calling
update-apt-xapian-index (there were comments in the IRC meeting[1] that
suggested that). So is the idea here to just tell apport to ignore crash
reports for /usr/sbin/update-apt-xapian-index during the upgrade? We
already do
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058227
Title:
Crash during upgrade from Mantic to
** Changed in: ubuntu-release-upgrader (Ubuntu)
Milestone: ubuntu-24.04-beta => ubuntu-24.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058227
Title:
Crash during upgrade from Mantic to
During the Foundations team meeting we talked about adding a quirk to
"turn off" a-x-i.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Milestone: None => ubuntu-24.04-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
19 matches
Mail list logo
