E: Internal Error, AutoRemover broke stuff

[Ken Sharp]

I'm trying to run a dist-upgrade, which should be simple enough, but it keeps failing at:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Hmm, seems like the AutoRemover destroyed something which really
shouldn't happen. Please file a bug report against apt.

The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libopenblas0-pthread : Depends: libgfortran5 (>= 8) but it is not going to be installed
E: Internal Error, AutoRemover broke stuff

libgfortran5 IS installed.

Package: libgfortran5
Version: 12.1.0-2ubuntu1~22.04
Priority: optional
Section: libs
Source: gcc-12
Origin: Ubuntu
Maintainer: Ubuntu Core developers <email address hidden>
Original-Maintainer: Debian GCC Maintainers <email address hidden>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 3,059 kB
Depends: gcc-12-base (= 12.1.0-2ubuntu1~22.04), libc6 (>= 2.34), libgcc-s1 (>= 4.3), libquadmath0 (>= 4.6)
Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2)
Homepage: http://gcc.gnu.org/
Task: kubuntu-desktop, kubuntu-full, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi
Download-Size: 882 kB
APT-Manual-Installed: no
APT-Sources: http://nova.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages

Apt says to report a bug against Apt, so here I am...

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apt 2.4.7
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Sep 22 13:09:38 2022
Ec2AMI: ami-0008be8e
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: None
Ec2InstanceType: vps2020-starter-1-2-20
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: Upgraded to jammy on 2022-08-15 (38 days ago)

[Julian Andres Klode (juliank)]

Thank you for your bug report. Please run APT_EDSP_DUMP_FILENAME=/tmp/lp1990525.edsp apt dist-upgrade --solver dump and attach /tmp/lp1990525.edsp to the bug (if that works).

If that does not work, please pass

-o Debug::pkgDepCache::Marker=1
-o Debug::pkgDepCache::AutoInstall=1
-o Debug::pkgProblemResolver=1

to the dist-upgrade and attach the output, and optimally also a tarball of /etc/apt /var/lib/apt/lists /var/lib/dpkg/status, e.g.

tar cJf lp1990525.tar.xz /etc/apt /var/lib/apt/lists /var/lib/dpkg/status

and attach the resulting tarball ` lp1990525.tar.xz`.

Also my hunch: Try passing -o APT::Get::Phase-Policy=1 to dist-upgrade and see if that works. This might be a regression from the new phaser (sigh).

[Ken Sharp (kennybobs)]

# APT_EDSP_DUMP_FILENAME=/tmp/lp1990525.edsp apt dist-upgrade --solver dump

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Execute external solver... Error!
The solver encountered an error of type: ERR_JUST_DUMPING
The following information might help you to understand what is wrong:
I am too dumb, i can just dump!
Please use one of my friends instead!

E: External solver failed with: I am too dumb, i can just dump!

Result is the same with the -o Debugs added (the files are identical).

# apt -o APT::Get::Phase-Policy=1 dist-upgrade

This doesn't complain anymore, but it does hold packages back.

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libpython3-dev libpython3-stdlib python3 python3-dev python3-distutils python3-gdbm python3-lib2to3 python3-minimal python3-tk
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.

[Julian Andres Klode (juliank)]

Sorry, "E: External solver failed with: I am too dumb, i can just dump!" is the expected output, this means it created the file.

[Julian Andres Klode (juliank)]

Ken, could you perhaps attach the /etc/machine-id or just comment the string in it? I can't find a machine-id that would trigger the bug.

[Julian Andres Klode (juliank)]

The other bug has more info so marking this as a duplicate as it's the same issue basically, same cause anyway.

[Ken Sharp (kennybobs)]

Machine ID for reference:
8e481f3e2b6240bebc283248d68a4af8