upgrade from 20.04 -> 22.04 fails due to python conflict from focal-updates repo

Bug #2009892 reported by Robin Battey
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
New
Undecided
Unassigned

Bug Description

I assumed this was due to me installing some random ppa from somewhere, but I eventually tracked this down to a conflict between python3-ldb and libldb2 from official repositories:

  2:2.4.4-0ubuntu0.20.04.1 from the focal-updates repo
  2:2.4.4-0ubuntu0.1 from the jammy-updates repo

I found this by updating apt with the jammy repos and running "apt-cache policy" on the broken packages, but you can see the package lists in the official locations for verification:

  https://packages.ubuntu.com/focal-updates/allpackages
  https://packages.ubuntu.com/jammy-updates/allpackages

This is not the only package, there are a number of python-related packages with this naming scheme, and I can't seem to get apt to resolve all of them. I can downgrade to the python version (2:2.0.8-2) in focal main, but then do-release-upgrade complains that I have updates.

I have worked around this by removing those packages (which also transitively removes: gnome-control-center gvfs-backends libsmbclient samba-libs ubuntu-desktop ubuntu-desktop-minimal vlc-plugin-samba), and then running the upgrade. But, this is clearly a bug in the upgrade process.
---
ProblemType: Bug
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-07-25 (957 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: ubuntu-release-upgrader (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
Tags: focal dist-upgrade
Uname: Linux 5.15.0-67-generic x86_64
UpgradeStatus: Upgraded to focal on 2023-03-09 (0 days ago)
UserGroups: N/A
_MarkForUpload: True
---
ProblemType: Bug
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-07-25 (957 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: ubuntu-release-upgrader (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
Tags: focal dist-upgrade
Uname: Linux 5.15.0-67-generic x86_64
UpgradeStatus: Upgraded to focal on 2023-03-09 (0 days ago)
UserGroups: N/A
_MarkForUpload: True
---
ProblemType: Bug
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-07-25 (957 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: ubuntu-release-upgrader (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
Tags: focal dist-upgrade
Uname: Linux 5.15.0-67-generic x86_64
UpgradeStatus: Upgraded to focal on 2023-03-09 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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

Can you please run apport-collect 2009892 so that the appropriate logs from the upgrade process are attached to this bug report?

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Revision history for this message
Robin Battey (zanfur) wrote : CurrentDmesg.txt.txt

apport information

tags: added: apport-collected dist-upgrade focal
description: updated
Revision history for this message
Robin Battey (zanfur) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeAptclonesystemstate.tar.gz

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeAptlog.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeLspcitxt.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeMainlog.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote :

I've given all relevant information already; you can readily see the conflict no matter what is on my system. The focal version is higher than the jammy version, so it fails to update.

But sure, done.

description: updated
Revision history for this message
Robin Battey (zanfur) wrote : CurrentDmesg.txt.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeAptclonesystemstate.tar.gz

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeAptlog.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeLspcitxt.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeMainlog.txt

apport information

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → New
description: updated
Revision history for this message
Robin Battey (zanfur) wrote : CurrentDmesg.txt.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeAptclonesystemstate.tar.gz

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeAptlog.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeLspcitxt.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote : VarLogDistupgradeMainlog.txt

apport information

Revision history for this message
Robin Battey (zanfur) wrote :

Apologies for the spam, it looked like apport collect failed the first time so I re-ran it.

To post a comment you must log in.