Internally, python-apt uses libapt-pkg, which for each package that has neither "Architecture: all" nor "MultiArch: same" properties generates a synthetic confclit with its own versions for other architectures. I.e. gnome-shell for amd64 conflicts with gnome-shell for i386, and vice versa, which makes sense.
However, python-apt fails to take architecture-specific conflicts (such as gnome-shell for amd64 conflicting with gnome-shell for i386) into account, and instead interprets them as plain conflicts of a package with itself.
I believe the attached python-apt.fix2.patch is a superficial fix that doesn't fix the real problem but happens to fix its symptom. I'll make another fix.
Internally, python-apt uses libapt-pkg, which for each package that has neither "Architecture: all" nor "MultiArch: same" properties generates a synthetic confclit with its own versions for other architectures. I.e. gnome-shell for amd64 conflicts with gnome-shell for i386, and vice versa, which makes sense.
However, python-apt fails to take architecture- specific conflicts (such as gnome-shell for amd64 conflicting with gnome-shell for i386) into account, and instead interprets them as plain conflicts of a package with itself.
I believe the attached python- apt.fix2. patch is a superficial fix that doesn't fix the real problem but happens to fix its symptom. I'll make another fix.