Comment 5 for bug 1993081

Looks like the culprit here is python3, as doing

  apt install python3:i386

causes the removal of several important packages. This in a Jammy LXD container and after doing `dpkg --add-architecture i386`.

The python3 package is marked Multi-Arch: allowed, so I would expect the i386 package to be co-installable without breaking the world, but I'm unsure on how this is supposed to be supported in Ubuntu (as Lucas mentioned i386 is not officially supported). Maybe we're just inheriting the Multi-Arch settings from Debian? I added a python3 task, let's see if we can get more information from a Python maintainer.

Relevant output (use `-o Debug::pkgProblemResolver=yes` for more verbosity):

root@paride-j:~# apt-get -s install python3.10-minimal:amd64 python3.10-minimal:i386
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3.10-minimal is already the newest version (3.10.6-1~22.04).
python3.10-minimal set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3.10-minimal : Conflicts: python3.10-minimal:i386 but 3.10.6-1~22.04 is to be installed
 python3.10-minimal:i386 : Recommends: python3.10:i386 but it is not going to be installed
                           Conflicts: python3.10-minimal but 3.10.6-1~22.04 is to be installed
E: Unable to correct problems, you have held broken packages.