Re: apt-get install wine32:i386 damaged my installation
On Sun, Dec 28, 2025 at 11:44:30 +0100, didier gaumet wrote:
> Le 28/12/2025 à 11:16, Nicolas George a écrit :
> > didier gaumet (HE12025-12-28):
> > > And there is the problem of multiarchitecture when you enable i386
> > > architecture, sometimes there are needed amd64 libraries that are replaced
> > > by i386 ones, breaking the system.
> >
> > Evidence required.
>
> Sorry, I have none to offer: this took place looooong ago.
>
> So let me reformulate it: perhaps this was due to me being dumb but needed
> amd64 libraries did get replaced by i386 ones and I suspect (without
> evidence, again) that at the time apt-get dependencies resolution process
> was not without reproach in this regard.
In a multiarch setup (i386 on amd64 for example), the shared library
packages can coexist. Each library package will have :i386 or :amd64
appended to its package name.
hobbit:~$ dpkg -l libc6\* | grep ^ii
ii libc6:amd64 2.41-12 amd64 GNU C Library: Shared libraries
ii libc6:i386 2.41-12 i386 GNU C Library: Shared libraries
ii libc6-dev:amd64 2.41-12 amd64 GNU C Library: Development Libraries and Header Files
The library -dev packages *cannot* coexist. You can have either
libc6-dev:amd64 or libc6-dev:i386 but not both at the same time.
Both packages would try to create headers such as /usr/include/stdio.h
and they could conflict.
Non-library packages also cannot coexist. You can't have two versions
of coreutils (for example) at the same time, because they would both
try to create /usr/bin/ls and other program files.
For the specific case of Wine, <https://wiki.debian.org/Wine> gives the
following recipe:
Install wine on a 64-bit architecture (amd64 with i386 as foreign
32-bit architecture):
sudo dpkg --add-architecture i386 && sudo apt update
sudo apt install \
wine \
wine32 \
wine64 \
libwine \
libwine:i386 \
fonts-wine
I would start there. This list does *not* include "wine:i386" or
"wine32:i386". The only explicit :i386 package named is "libwine:i386".
Reply to: