Ubuntu
ubuntu-release-upgrader package

do-release-upgrade fails with no error

Bug #1921593 reported by Malte Jan Kaffenberger
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

$ lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.42
ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
Uname: Linux 4.15.0-139-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
Date: Sat Mar 27 19:10:01 2021
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-03-27 (0 days ago)

Revision history for this message
Malte Jan Kaffenberger (maltejk) wrote :
Brian Murray (brian-murray)
tags: added: rls-ff-incoming
Revision history for this message
Brian Murray (brian-murray) wrote :

From Mainlog.txt:

2021-03-27 19:07:33,802 DEBUG The package 'e2fsprogs' is marked for removal but it's an ESSENTIAL package
2021-03-27 19:07:33,828 ERROR Dist-upgrade failed: 'The essential package 'e2fsprogs' is marked for removal.'

We should sort out why es2fsprogs was marked for removal.

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

You seem to have installed some packages from the release of Ubuntu to which you are trying to upgrade (Ubuntu 20.04) on your system and that is likely breaking the ability to calculate the upgrade. The problematic packages are likely libpython2-stdlib python-is-python2 python2 and python2-minimal. Please try removing those packages and then upgrading again.

The complete list of strange packages follows:

Installed in the clone-file but not in the system:

borgmatic gcc-10-base libcrypt-dev libcrypt1 libgcc-s1 libpython2-stdlib python-is-python2 python2 python2-minimal python3-pykwalify

tags: removed: rls-ff-incoming
Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Revision history for this message
Malte Jan Kaffenberger (maltejk) wrote :

Thank you for the hints, Brian!

There are some things I noticed which may have lead to the error:

- I had packages installed from 20.04 already
- packages from bionic were pinned to lower priority

The upgrade succeeded after removing the pin.

This issue can be closed I guess.

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

Other bug subscribers

Remote bug watches

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