Ubuntu
ubuntu-release-upgrader package

Cannot upgrade 20.04.3 LTS ot 22.04.1 LTS

Asked by Robert Navarro

lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release: 20.04

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done

Calculating the changes

Calculating the changes

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad PPA and
try the upgrade again.

If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
you want to investigate this yourself the log files in
'/var/log/dist-upgrade' will contain details about the upgrade.
Specifically, look at 'main.log' and 'apt.log'.

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.36
ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
Uname: Linux 5.4.0-90-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 19 15:17:28 2022
InstallationDate: Installed on 2017-11-02 (1782 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2022-09-19 (0 days ago)

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu ubuntu-release-upgrader Edit question
Assignee:
No assignee Edit question
Solved by:
Robert Navarro
Solved:
Last query:
Last reply:

This question was originally filed as bug #1990197.

Revision history for this message
Aaron Rainbolt (arraybolt3) said : 		#1

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. If you would prefer live chat support, you can find an IRC support channel for your flavor of Ubuntu here: https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Aaron Rainbolt (arraybolt3) said : 		#2

You probably need to run "sudo apt update && sudo apt full-upgrade" first. If you're on Ubuntu 20.04.3, that's a likely indicator that your system hasn't been updated, since the current point release of Ubuntu 20.04 is 20.04.5.

Revision history for this message
Aaron Rainbolt (arraybolt3) said : 		#3

Also, remember to back up all your data before attempting to upgrade. (Make sure that you include passwords in your browsers and password managers, as well as any encryption keys you generated.)

Revision history for this message
Robert Navarro (crshman) said : 		#4

Wow I feel really dumb.

I've been googling this issues for weeks and finally decided to create the bug report.

You immediately caught that I was stuck on 20.04.3, so I did some digging.

Turns out the mirror I had in my sources.list wasn't syncing with the upstream mirrors correctly so I was "stuck" behind.

I just switched back to the default us.archive.ubuntu.com mirror and there were 500+ packages that needed updating.

Sorry for the noise here.

I'll try do-release-upgrade after the updates finish and I'll close this issue if it succeeds.

Revision history for this message
Robert Navarro (crshman) said : 		#5

Yep that fixed it, sorry for missing the minor detail!

Revision history for this message
Aaron Rainbolt (arraybolt3) said : 		#6

Nice! Glad to be able to help!