Upgrade error (20.04 to 22.04): Could not calculate the upgrade | An unresolvable problem occurred while calculating the upgrade.

Bug #1986409 reported by coffeepixel
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

sudo do-release-upgrade -d

Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1.267 kB]
Fetched 1.268 kB in 0s (0 B/s)
authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg'
extracting 'jammy.tar.gz'

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://archive.ubuntu.com/ubuntu focal InRelease
Hit http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit http://archive.ubuntu.com/ubuntu focal-security InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
None

Checking for installed snaps

Calculating snap size requirements

Updating repository information
Hit http://archive.ubuntu.com/ubuntu jammy InRelease
Hit http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit http://archive.ubuntu.com/ubuntu jammy-security InRelease
Fetched 0 B in 0s (0 B/s)

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 caused by:
* Upgrading to a pre-release version of Ubuntu
This is most likely a transient problem,
please try again later.
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.38
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 12 22:04:33 2022
InstallationDate: Installed on 2021-10-11 (305 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2022-08-13 (0 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
coffeepixel (coffeepixel) wrote :
Revision history for this message
coffeepixel (coffeepixel) wrote :

I really can't update to 22.04 and I don't know what to do. I've researched what could be done, but it didn't solve the problem.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
summary: - Upgrade error (20.04 to 22.04)
+ Upgrade error (20.04 to 22.04): Could not calculate the upgrade | An
+ unresolvable problem occurred while calculating the upgrade.
Revision history for this message
Nick Rosbrook (enr0n) wrote :

Based on the contents of VarLogDistupgradeAptlog.txt, it looks like you installed python3 from the deadsnakes PPA at some stage. There are several lines in that log that look like this:

python3.10-dev:amd64 Depends on python3.10:amd64 < 3.10.6-1+focal1 @ii mK > (= 3.10.4-3ubuntu0.1) can't be satisfied!

You can use the `ppa-purge` tool to remove packages that were installed from the deadsnakes PPA, and then try the upgrade again.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
coffeepixel (coffeepixel) wrote :

What's the safest way to do this?

Revision history for this message
coffeepixel (coffeepixel) wrote :

I removed the ppa packages and I still can't upgrade...

Is there anything else I can do?

Revision history for this message
Nick Rosbrook (enr0n) wrote :

What exactly did you try to remove the pacakges? I am able to purge these packages by running:

$ ppa-purge deadsnakes/ppa

Revision history for this message
coffeepixel (coffeepixel) wrote :

I just went to the Other Software tab of Software and Updates and removed the ppa packages.

Then I checked using apt policy and there were no more ppa packages...

Revision history for this message
Nick Rosbrook (enr0n) wrote :

Please check which version of python3.10 you have installed currently:

$ apt-cache policy

If you still have 3.10.6-1+focal1, then the PPA packages have not been purged yet, in which case you should try:

$ apt purge python3.10

Revision history for this message
coffeepixel (coffeepixel) wrote :

I checked with apt-cache policy and didn't find it. To be sure, I checked the installed versions of Python:

➜ ~ python --version
Python 2.7.18
➜ ~ python3 --version
Python 3.8.10

Revision history for this message
Nick Rosbrook (enr0n) wrote :

Please open a new bug report with the logs from your most recent upgrade attempt.

Revision history for this message
coffeepixel (coffeepixel) wrote :
Revision history for this message
coffeepixel (coffeepixel) wrote :

I was able to upgrade after removing python3.10.

Thanks for your help with the upgrade!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.