Control: severity -1 serious On Fri, Jul 31, 2026 at 05:18:51PM +0100, Tim Colgate wrote: > Package: libopenmpi40 > Version: 5.0.10-1 > Severity: important > X-Debbugs-Cc: [email protected] > > Dear Maintainer, > > I attempted to install a package but apt reported it was in a broken state, > it suggested "--fix-broken install" > > # apt --fix-broken install > ... > Continue? [Y/n] > Get:1 http://deb.debian.org/debian testing/main amd64 libopenmpi40 amd64 > 5.0.10-1 [2,018 kB] > Fetched 2,018 kB in 0s (5,938 kB/s) > Reading changelogs... Done > Extracting templates from packages: 100% > (Reading database… 641841 files and directories currently installed.) > Preparing to unpack …/libopenmpi40_5.0.10-1_amd64.deb… > Unpacking libopenmpi40:amd64 (5.0.10-1)… > dpkg: error processing archive > /var/cache/apt/archives/libopenmpi40_5.0.10-1_amd64.deb (--unpack): > trying to overwrite '/usr/lib/x86_64-linux-gnu/libmpi.so.40', which is also > in package libopenmpi3t64:amd64 (4.1.6-13.3) > Errors were encountered while processing: > /var/cache/apt/archives/libopenmpi40_5.0.10-1_amd64.deb > Error: Sub-process /usr/bin/dpkg returned an error code (1) > # >...
The Breaks+Replaces: libopenmpi3, libopenmpi3t64 in libopenmpi40 should be restored, due to various reasons good and bad it is not particularly rare that people have stale old packages installed. There are also no serious benefits when dropping such relationships. cu Adrian
