On Thu, Jan 09, 2025 at 08:27:13AM +0100, Helmut Grohne wrote:
> lib32atomic1 and libn32atomic1 have an undeclared cross-architecture
> file conflict on /usr/lib32/libatomic.so.1 and
> /usr/lib32/libatomic.so.1.2.0. This applies to bullseye, bookworm,
> trixie and sid. I am not aware of any use case for coinstalling them and
> it also does not work. Please have them declare Conflicts with one
> another.

This applies likewise to:

 * lib32gcc-s1 vs libn32gcc-s1
 * lib32gfortran5 vs libn32gfortran5
 * lib32go19 vs libn32go19
 * lib32go21 vs libn32go21
 * lib32gomp1 vs libn32gomp1
 * lib32gphobos2 vs libn32gphobos2
 * lib32gphobos3 vs libn32gphobos3
 * lib32objc4 vs libn32objc4
 * lib32stdc++6 vs libn32stdc++6
 * lib32stdc++6-9-dbg vs libn32stdc++6-9-dbg
 * lib32stdc++6-10-dbg vs libn32stdc++6-{9,10}-dbg
 * lib32stdc++6-11-dbg vs libn32stdc++6-{9,10,11,12,13,14,15}-dbg
 * lib32stdc++6-12-dbg vs libn32stdc++6-{9,10,11,12,13,14,15}-dbg
 * lib32stdc++6-13-dbg vs libn32stdc++6-{9,10,11,12,14,15}-dbg
 * lib32stdc++6-14-dbg vs libn32stdc++6-{9,10,11,12,13,15}-dbg
 * lib32stdc++6-15-dbg vs libn32stdc++6-{9,10,11,12,13,14}-dbg

Helmut

Reply via email to