22.04 is suggested on Ubuntu's website but not in the repository

$ sudo do-release-upgrade -c # It SHOULD work as 22.04 is released now
Checking for a new Ubuntu release
No new release found.
$ sudo do-release-upgrade -d # This is the only solution now which is abnormal
Checking for a new Ubuntu release

= Welcome to the Ubuntu 'Jammy Jellyfish' development release =

''This release is still in development.''

The current mirror is archive.ubuntu.com. The current OS is 21.10.

Here is Solutions:

We have many solutions to this problem, But we recommend you to use the first solution because it is tested & true solution that will 100% work for you.

Solution 1

The ISO has been released for new installs, upgrades from 21.10 are not yet opened up which is normal. The earliest they’ll open up is next week just like every prior cycle.

For users of 20.04 LTS, the release-upgrade will not be seen until after the release of Ubuntu 22.04.1 LTS as per documentation and prior cycles; ie. about a further three months wait – as it’s assumed LTS users prize stability.

If you look at the file https://changelogs.ubuntu.com/meta-release you’ll see why you’re getting the behavior you’re experiencing; as Ubuntu Release Team make that change (allowing upgrades) when they deem it fit and ready for existing users.

At this moment in time, as stated, Ubuntu 22.04 LTS is deemed fit for new installs.

If you don’t want to wait; you can use the -d option which will cause the following file to be used instead https://changelogs.ubuntu.com/meta-release-development thus the path will be seen.

Those files will be changed when the Ubuntu Release Team deem the systems ready for users, the aim of which is to ensure stability for existing users.

Solution 2

Generally the do-release-upgrade option will not show .0 releases. When the first point-release, Ubuntu 22.04.1, is made available later this year, people will be able to upgrade their installations via the do-release-upgrade option.

In the meantime, you can use -d to install the current stable release (despite the -d meaning "development release").

Note: Use and implement solution 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply