https://bugs.winehq.org/show_bug.cgi?id=54661
--- Comment #12 from François Gouget fgouget@codeweavers.com --- I can reproduce the dependency issue on both Debian 11.6 and Debian Testing with this apt command (same with apt-get):
apt install libpcsclite-dev:amd64 libpcsclite-dev:i386
It essentially wants to replace python3:amd64 with python3:i386 with cascading effects on all packages that depend on python3.
However I discovered that I don't have any issue if I install libpcsclite-dev:i386 using aptitude. I also don't have any issue if I run this 'very different' apt command!
apt install libpcsclite-dev:i386 libpcsclite-dev:amd64
Order... matters??? I did not know that.
I also found a couple more resilient options:
# Assume python3 is already installed anyway apt install --no-install-recommends libpcsclite-dev:i386 libpcsclite-dev:amd64
or # Override apt's conflict resolution algorithm apt install libpcsclite-dev:i386 libpcsclite-dev:amd64 python3+
So I'd say it's more an issue of apt being silly (why prioritize the uninstalled i386 recommends over the already installed amd64 ones) more than a libpcsclite-dev issue. So I won't file a Debian bug.