3

This is what I get when I try to upgrade mate from 19.10 to 20.04:

mae@HP-Compaq-6715b-Ubuntu-MATE:~$ sudo bash
[sudo] password for mae: 
root@HP-Compaq-6715b-Ubuntu-MATE:/home/mae# do-release-upgrade 

Checking for a new Ubuntu release

No new release found.

root@HP-Compaq-6715b-Ubuntu-MATE:/home/mae#
Saxtheowl
  • 1,609
  • 2
  • 9
  • 20
Mark Emanuele
  • 31
  • 1
  • 2
    Does this answer your question? [Is the "Final Release" a "Development Release"?](https://askubuntu.com/questions/1229890/is-the-final-release-a-development-release) Specifically the final bullet of https://askubuntu.com/a/1229900/19626 – user535733 Apr 24 '20 at 21:53
  • I'm also unable to upgrade to 20.04. A fresh installation from the iso worked fine on another PC but that's not an option for my main setup. – OpenTangent Apr 25 '20 at 08:25
  • [Wait until 20.04.1 (aka "the first point release")](https://askubuntu.com/a/125492/11316) arrives. But I agree, this is rather unfortunate. You can "force" it with `-d`, I think. – 0xC0000022L Apr 29 '20 at 09:40
  • The forcing method is in my answer (which is older than your comment). – nift4 May 02 '20 at 10:26

2 Answers2

2

If you don't want to wait until it's unlocked for upgrading, run do-release-upgrade -dc. If you get 20.04 run do-release-upgrade -d to install.

nift4
  • 86
  • 5
1

You're not alone. do-release-upgrade doesn't work for me either from 19.10. No sign of 20.04 for me. I am uncertain how soon the update repositories are available. I assumed from the day of release. Some have suggested adding the development builds with the -d option but I want the normal update option.

This article suggests upgrades this way will happen a few days after the official release so we just need to be patient I guess.

https://linuxconfig.org/how-to-upgrade-ubuntu-to-20-04-lts-focal-fossa

markrich
  • 1,390
  • 3
  • 16
  • 27
  • [This answer](https://askubuntu.com/a/125492/11316)) provides the main reason and the other answer _here_ provides the workaround (`-d`). – 0xC0000022L Apr 29 '20 at 09:40
  • This has become available today (7/5/20) properly, without using the dodgy development option via regular software updates, however, the documentation still says it is and should not be installed. Previous releases never made this an issue. Someone needs to fix this messy confusion on published vs development. If it's out it's not development. – markrich May 07 '20 at 17:06