upgrade from 18.04 to 20.04 fails to calculate if libomp5 is installed

Bug #1886748 reported by Luca Bognolo
380
This bug affects 63 people
Affects Status Importance Assigned to Milestone
llvm-toolchain-10 (Ubuntu)
High
Unassigned
Focal
High
Unassigned
llvm-toolchain-9 (Ubuntu)
High
Unassigned
Focal
High
Unassigned

Bug Description

~$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [1,554 B]
Get:2 Upgrade tool [1,342 kB]
Fetched 1,343 kB in 0s (0 B/s)
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg'
extracting 'focal.tar.gz'

Reading cache

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

Updating repository information
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)

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 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
Uname: Linux 4.15.0-109-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Wed Jul 8 13:26:03 2020
InstallationDate: Installed on 2018-02-19 (869 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-07-08 (0 days ago)

Revision history for this message
Luca Bognolo (m01l17c21r18) wrote :
summary: - upgrade from 18.04 to 20.04 fails
+ upgrade from 18.04 to 20.04 fails to calculate with clang-6.0 and pocl-
+ opencl-icd installed
Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
importance: Undecided → High
tags: added: rls-ff-incoming
Revision history for this message
Brian Murray (brian-murray) wrote : Re: upgrade from 18.04 to 20.04 fails to calculate with clang-6.0 and pocl-opencl-icd installed

I was able to recreate the failure to calculate the upgrade by installing the packages clang-6.0 and pocl-opencl-icd.

Revision history for this message
Luca Bognolo (m01l17c21r18) wrote :

I uninstalled clang-6.0 and the update now seems to proceed fine. Thank you Brian!

Changed in ubuntu-release-upgrader (Ubuntu Focal):
status: New → Confirmed
importance: Undecided → High
tags: removed: rls-ff-incoming
Revision history for this message
Brian Murray (brian-murray) wrote :

The following bug reports may be duplicates of this bug.

 $ for log in $(find . -name VarLogDistupgradeAptlog.txt); do grep -H -m 1 "libomp5:amd64 rather than change libomp5-10:amd64" $log; done
./bug-1885521/VarLogDistupgradeAptlog.txt: Holding Back libomp5:amd64 rather than change libomp5-10:amd64
./bug-1885962/VarLogDistupgradeAptlog.txt: Holding Back libomp5:amd64 rather than change libomp5-10:amd64
./bug-1876395/VarLogDistupgradeAptlog.txt: Holding Back libomp5:amd64 rather than change libomp5-10:amd64
./bug-1876536/VarLogDistupgradeAptlog.txt: Holding Back libomp5:amd64 rather than change libomp5-10:amd64
./bug-1884791/VarLogDistupgradeAptlog.txt: Holding Back libomp5:amd64 rather than change libomp5-10:amd64

tags: added: id-5f22e5bec689a98b273b7d91
Revision history for this message
Brian Murray (brian-murray) wrote :

Removing libomp5 after adjusting sources.list from bionic to focal allows the upgrade to calculate.

bdmurray@clean-bionic-amd64:~$ sudo apt-get remove libomp5
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libomp-dev:amd64 < 5.0.1-1 -> 1:10.0-50~exp1 @ii umU Ib >
Broken libomp-dev:amd64 Depends on libomp-10-dev:amd64 < none | 1:10.0.0-4ubuntu1 @un uH > (>= 10~)
  Considering libomp-10-dev:amd64 0 as a solution to libomp-dev:amd64 0
  Re-Instated libomp5-10:amd64
  Re-Instated gcc-10-base:amd64
  Re-Instated libgcc-s1:amd64
  Re-Instated libomp-10-dev:amd64
  Re-Instated libomp-dev:amd64
Done
The following additional packages will be installed:
  gcc-10-base libgcc-s1 libomp-10-dev libomp-dev libomp5-10
Suggested packages:
  libomp-10-doc
The following packages will be REMOVED:
  libomp5
The following NEW packages will be installed:
  gcc-10-base libgcc-s1 libomp-10-dev libomp5-10
The following packages will be upgraded:
  libomp-dev
1 upgraded, 4 newly installed, 1 to remove and 1409 not upgraded.
Need to get 411 kB of archives.
After this operation, 1,863 kB of additional disk space will be used.

Revision history for this message
Brian Murray (brian-murray) wrote :

Additionally, installing libomp5-10 right attempting the upgrade allowed the upgrade to calculate.

summary: - upgrade from 18.04 to 20.04 fails to calculate with clang-6.0 and pocl-
- opencl-icd installed
+ upgrade from 18.04 to 20.04 fails to calculate if libomp5 is installed
Revision history for this message
JP (jptech) wrote :

I confirm, it works with your solution Brian.
Thank you :-)

Revision history for this message
Brian Murray (brian-murray) wrote :

Modifying the Breaks: section of the packages file for libomp5-9 and libomp5-10 so that its "Breaks: (<< 3.7-1)" also allowed the upgrade to calculate so we could SRU llvm-toolchain-9 and llvm-toolchain-10 so that upgrades work without people having to do anything.

Revision history for this message
Brian Murray (brian-murray) wrote :

Julian suggested moving the clang-9 Recommends of libomp-9-dev to a Suggests and that also allowed the upgrade to complete.

Revision history for this message
Steve Langasek (vorlon) wrote :

Breaks without Replaces is highly unusual, and in this case a versioned Replaces in addition to the Breaks would be correct. It may help with the upgrade calculation.

Revision history for this message
Brian Murray (brian-murray) wrote :

I tested a release upgrade from bionic to focal with my PPA enabled which has version of libomp5-9 and libomp5-10 which Break and Replace on libomp5 (<<5.0.1-1). While the upgrade proceeded and succeeded libomp5 from bionic was still installed on the system.

root@clean-bionic-amd64:~# apt-cache policy libomp5
libomp5:
  Installed: 5.0.1-1
  Candidate: 1:10.0-50~exp1
  Version table:
     1:10.0-50~exp1 500
        500 http://192.168.10.7/ubuntu focal/universe amd64 Packages
 *** 5.0.1-1 100
        100 /var/lib/dpkg/status

Attached are log files from the upgraded.

Revision history for this message
Brian Murray (brian-murray) wrote :

I tested a second upgrade from bionic to focal with my PPA enabled and this time libomp5 was identified as an "Unused dependencies" and a "remove_candidates". However, this time it was actually marked for removal while previously this appeared in /var/log/dist-upgrade/main.log:

 2020-08-22 09:49:11,854 DEBUG package 'libomp5' produces an unwanted removal 'gnome-software-plugin-snap', skipping
 2020-08-22 09:49:12,751 DEBUG 'libomp5' scheduled for remove but not safe to remove, skipping

So I think the debian/control changes in the PPA work but something else is wrong with the release-upgrader and the snap removal work.

Revision history for this message
Brian Murray (brian-murray) wrote :

Actually, its nothing to with snaps - that package just has the word snap in it. So something seems wrong with the process which finds unwanted removals.

Revision history for this message
Brian Murray (brian-murray) wrote :

I've discovered what is wrong with the unwanted removals and that is tracked in bug 1894919.

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

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

Changed in llvm-toolchain-10 (Ubuntu Focal):
status: New → Confirmed
Changed in llvm-toolchain-10 (Ubuntu):
status: New → Confirmed
Changed in llvm-toolchain-9 (Ubuntu Focal):
status: New → Confirmed
Changed in llvm-toolchain-9 (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

This is actually a bug with the llvm package relationships and not one with ubuntu-release-upgrader.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Invalid
Changed in ubuntu-release-upgrader (Ubuntu Focal):
status: Confirmed → Invalid
Revision history for this message
kcroot (krzysiekcybura) wrote :

I installed clang-9 package, calculations of upgrade running fine.

Revision history for this message
FredrikAgert (fredrik-agert) wrote :

I also installed clang-9, and calculation of upgrade is running fine. Finally I can update. Thank you all especially Brian-Murray.

Revision history for this message
kcroot (krzysiekcybura) wrote :

Sorry i forget to thanks all support guys especially Brian-Murray.

Mathew Hodson (mhodson)
no longer affects: ubuntu-release-upgrader (Ubuntu Focal)
no longer affects: ubuntu-release-upgrader (Ubuntu)
Changed in llvm-toolchain-10 (Ubuntu):
importance: Undecided → High
Changed in llvm-toolchain-10 (Ubuntu Focal):
importance: Undecided → High
Changed in llvm-toolchain-9 (Ubuntu):
importance: Undecided → High
Changed in llvm-toolchain-9 (Ubuntu Focal):
importance: Undecided → High
To post a comment you must log in.