Problem Description:
On Ubuntu 25.10 do-release-upgrade says “no new release” regardless of the option in /etc/update-manager/release-upgrades. Waiting for point-release? I remember upgrade was waiting point-release only for upgrade from preceding LTS. I’m wrong? Thanks.
corrado@corrado-n5-questing:~$ cat /etc/update-manager/release-upgrades | grep Prompt
Prompt=lts
corrado@corrado-n5-questing:~$ sudo do-release-upgrade
Checking for a new Ubuntu release
There is no development version of an LTS available.
To upgrade to the latest non-LTS development release
set Prompt=normal in /etc/update-manager/release-upgrades.
corrado@corrado-n5-questing:~$ cat /etc/update-manager/release-upgrades | grep Prompt
Prompt=normal
corrado@corrado-n5-questing:~$ sudo do-release-upgrade
Checking for a new Ubuntu release
No new release found.
Won't: sudo do-release-upgrade -d
Upgrade to 26.10?
AI replied:
That is a very sharp observation, but in this specific timing, the answer is no. Here is why that command won’t accidentally bump you to 26.10:
1. The Release Cycle Timing
Ubuntu 26.10 (the "Interim" release following the LTS) is currently in its very early Development stage.
* April 2026: 26.04 LTS is released.
* May 2026 (Now): Work on 26.10 has only just begun.
* October 2026: 26.10 is actually released.
The do-release-upgrade -d command looks for the "Development" release. However, Canonical doesn't typically make the next version available via the upgrade tool until the "Toolchain Upgrade" and "Alpha" milestones are reached, which usually happens later in the summer.
@corradoventu, according to the upgrade guide, 26.04 should already be available for release upgrade from 25.10.
I’d start by making sure everything is up-to-date, including the release upgrader:
sudo apt upgrade --update
And then check again.
It may also be related to that dreadful DDoS, which still seems to be ongoing, but I have no insights into that; just throwing things at the wall to see what sticks.
What happens if you run do-release-upgrade like so
$ DEBUG_UPDATE_MANAGER=1 do-release-upgrade -d
On my 24.04 system I get:
Checking for a new Ubuntu release
MetaRelease.__init__() useDevel=True useProposed=False
/etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release
/etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release-lts
/etc/update-manager/meta-release: -development
/etc/update-manager/meta-release: -proposed
metarelease-uri: https://changelogs.ubuntu.com/meta-release-lts-development
MetaRelease.download()
have self.metarelease_information
MetaRelease.parse()
current dist name: 'noble'
found distro name: 'noble'
found distro name: 'resolute'
new dist: <UpdateManager.Core.MetaRelease.Dist object at 0x7cd56cd563c0>
trying to find suitable mirror
mirror_from_sources_list: noble
no mirror found
url_downloadable: http://archive.ubuntu.com/ubuntu/dists/resolute/main/dist-upgrader-all/current/ReleaseAnnouncement?lang=en_US
s='http' n='archive.ubuntu.com' p='/ubuntu/dists/resolute/main/dist-upgrader-all/current/ReleaseAnnouncement' q='lang=en_US'
The rest is a welcome message for 26.04 and a prompt to continue with upgrade
Aside from the expected difference in the current dist name (noble vs. questing), I’m curious what result you get.
update-manager is different between Noble and Questing and this may be a BUG because 25.10 EOL is 01 Jul 2026 so before 26.04 point release 09 Jul 2026
corrado@corrado-n5-questing:~$ DEBUG_UPDATE_MANAGER=1 do-release-upgrade
Checking for a new Ubuntu release
MetaRelease.__init__() useDevel=False useProposed=False
/etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release
/etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release-lts
/etc/update-manager/meta-release: -development
/etc/update-manager/meta-release: -proposed
metarelease-uri: https://changelogs.ubuntu.com/meta-release
MetaRelease.download()
have self.metarelease_information
MetaRelease.parse()
current dist name: 'questing'
found distro name: 'warty'
found distro name: 'hoary'
found distro name: 'breezy'
...........
found distro name: 'mantic'
found distro name: 'noble'
found distro name: 'oracular'
found distro name: 'plucky'
found distro name: 'questing'
found distro name: 'resolute'
No new release found.
corrado@corrado-n5-questing:~$
Dist: questing
Name: Questing Quokka
Version: 25.10
Date: Thu, 09 October 2025 00:25:10 UTC
Supported: 1
Description: This is the 25.10 release
Release-File: http://archive.ubuntu.com/ubuntu/dists/questing-updates/Release
ReleaseNotes: http://archive.ubuntu.com/ubuntu/dists/questing-updates/main/dist-upgrader-all/current/ReleaseAnnouncement
ReleaseNotesHtml: http://archive.ubuntu.com/ubuntu/dists/questing-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/questing-updates/main/dist-upgrader-all/current/questing.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/questing-updates/main/dist-upgrader-all/current/questing.tar.gz.gpg
Dist: resolute
Name: Resolute Raccoon
Version: 26.04 LTS
Date: Thu, 23 April 2026 00:26:04 UTC
Supported: 0
Description: This is the 26.04 LTS release
Release-File: http://archive.ubuntu.com/ubuntu/dists/resolute/Release
ReleaseNotes: http://archive.ubuntu.com/ubuntu/dists/resolute/main/dist-upgrader-all/current/ReleaseAnnouncement
ReleaseNotesHtml: http://archive.ubuntu.com/ubuntu/dists/resolute/main/dist-upgrader-all/current/ReleaseAnnouncement.html
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/resolute/main/dist-upgrader-all/current/resolute.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/resolute/main/dist-upgrader-all/current/resolute.tar.gz.gpg
When “Supported: 0” is changed to “Supported: 1” for resolute, 25.10 users will be able to use do-release-upgrade to upgrade to 26.04 without using “-d” or “-p” (24.04 will be able to do this in August). If you check the date stamps on the meta-release* file in changelogs.ubuntu.com you’ll see they haven’t been updated since the release date of Resolute. And none them have entries for Stonking. So as far as update-manager and do-release-upgrade are concerned, Stonking doesn’t exist yet, and resolute is still considered a development release which is unsupported. Which is why I can specify “do-release-upgrade -d” on my 24.04 system and get offered to upgrade to 26.04 because “-d” and “-p” ignores the “Supported:” key if its set to “0”.
What I’m not sure about is whether going from an interim release like 25.10 to 26.04 is handled differently by do-release-upgrade than lts-to-lts-development. I don’t think it should, but unless @corradoventu confirms I won’t know for sure and I’m not motivated to spin up a 25.10 vm to check it out.
It’s handled similarly in that there is a delay before the upgrade window opens…as you already know. The interim-to-LTS delay only occurs during LTS releases.
It’s handled differently in that the delay won’t be three months, which is when the LTS-to LTS window opens.
I made a point of doing a clean install of 25.10 and fully updated it and then a distribution upgrade to 26.04 after holding the Yaru icons to see if it could be done. I did not have any issues.
I have one installation of 24.04 (Noble) that stalls at calculating the changes and reverts everything.
corrado@corrado-n2-noble:~$ DEBUG_UPDATE_MANAGER=1 do-release-upgrade
Checking for a new Ubuntu release
MetaRelease.__init__() useDevel=False useProposed=False
/etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release
/etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release-lts
/etc/update-manager/meta-release: -development
/etc/update-manager/meta-release: -proposed
metarelease-uri: https://changelogs.ubuntu.com/meta-release-lts
MetaRelease.download()
have self.metarelease_information
MetaRelease.parse()
current dist name: 'noble'
found distro name: 'dapper'
found distro name: 'hardy'
found distro name: 'lucid'
found distro name: 'precise'
found distro name: 'trusty'
found distro name: 'xenial'
found distro name: 'bionic'
found distro name: 'focal'
found distro name: 'jammy'
found distro name: 'noble'
found distro name: 'resolute'
There is no development version of an LTS available.
To upgrade to the latest non-LTS development release
set Prompt=normal in /etc/update-manager/release-upgrades.
corrado@corrado-n2-noble:~$
