Package: libboost-chrono1.90.0 Version: 1.90.0-5+b1 Severity: normal Dear Maintainer,
$ sudo apt install libboost-chrono1.90.0:i386 [...] Selecting previously unselected package libboost-chrono1.90.0:i386. (Reading database… 1687902 files and directories currently installed.) Preparing to unpack …/libboost-chrono1.90.0_1.90.0-5+b1_i386.deb… Unpacking libboost-chrono1.90.0:i386 (1.90.0-5+b1)… dpkg: dependency problems prevent configuration of libboost-chrono1.90.0:i386: libboost-chrono1.90.0:amd64 (1.90.0-5+b1) breaks libboost-chrono1.88.0t64 and is installed. libboost-chrono1.90.0:i386 (1.90.0-5+b1) provides libboost-chrono1.88.0t64. I first encountered it during an apt full-upgrade. It is quite bad because it only manifests at configuration time, whereas dependency issues usually manifest much earlier, safely refusing to upgrade. Multiarch used to work fine with 1.83. (thank you for updating to 1.90, by the way) -- System Information: Debian Release: forky/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-debug'), (500, 'testing'), (400, 'stable-security'), (400, 'stable'), (50, 'unstable-debug'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64, ppc64el, s390x, armhf Kernel: Linux 6.16.9+deb14-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libboost-chrono1.90.0 depends on: ii libc6 2.42-13 ii libgcc-s1 16-20260308-1 ii libstdc++6 16-20260308-1 libboost-chrono1.90.0 recommends no packages. libboost-chrono1.90.0 suggests no packages. -- no debconf information
