44

I want to use do-release-upgrade to upgrade from 18.04 to 20.04, but I can't do that

do-release-upgrade
Checking for a new Ubuntu release
There is no development version of an LTS available.

It seems that this file is used, and it still points to 18.04.

Do you know when (or how?) can I upgrade to 20.04?

  • 2
    Please update the status when the bug is fixed. Thanks – e2-e4 Aug 14 at 7:03
  • If you don't want to wait, an official blog tells you how - ubuntu.com/blog/… – guiverc Aug 20 at 22:30
78

See https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-status-tracking/17604 for the current status.

On 25 September 2020, the final upgrade-blocking bug was closed.

If you are reading this on 25-27 September, just be patient while your local mirror catches up.

| improve this answer | |
  • Your answer is super useful. I just wanted to suggest to keep all the historic (i.e. the previous dates you mentionned). – Mathieu Dubois Sep 4 at 8:10
  • It suggests that this launchpad bug is blocking upgrades, but yet the launchpad janitor claims that a fix has been released? – starbeamrainbowlabs Sep 4 at 14:25
  • @starbeamrainbowlabs I understood what the OP mean; I noticed that he removed the point as of August 27th (when 2 bugs were blocking) and I think that this historic information is valuable. – Mathieu Dubois Sep 4 at 19:23
  • 4
    @starbeamrainbowlabs read the Launchpad Janitor message closely. It has been resolved for Groovy only...and no others yet. Historical data is conveniently available in the edit history of the discourse thread. – user535733 Sep 4 at 19:32
9
sudo do-release-upgrade -d

Will get you safely upgraded today, but please verify before upgrading that you are not affected by the blocking bugs mentioned above by user535733.

| improve this answer | |
  • 2
    This is actually better than manually editing sources.list. – Kulfy Aug 18 at 18:55
  • This works because 20.04 is still flagged as a developmental release until they sort out those blocking bugs. Since 19.10 is no longer the most recent developmental release, upgrading this way with the "-d" flag is the simplest way to upgrade "now" before 20.04 is formally flagged as LTS, and it won't compromise your preference to stick to future LTS releases going forward. – Jeff Sereno Aug 18 at 22:28
  • 2
    The remaining blocking bug, in layman's terms is a problem in certain cloud environments, where a disk boot record is not used. If your system uses a physical disk, the bug should not be able to affect you and you can safely upgrade. – DustWolf Sep 5 at 15:06
  • -d does not work for me (18.04.1), and apparently I'm not the only one. askubuntu.com/questions/1254519/… – Costin Gușă Sep 9 at 17:45
3

If you have a 32-bit installation then you will never be offered an upgrade to 20.04 because it is not supported anymore. If this is the case then your only way is to reinstall with the 64-bit version ;-(

How to check quickly: In a terminal enter

uname -m

If this gives you i686 and not x86_64 then you have 32-bit installation.

Hope that helps

| improve this answer | |

Not the answer you're looking for? Browse other questions tagged or ask your own question.