Source: mimalloc Version: 3.0.1+ds-2+b1 Severity: important Dear Maintainer,
trying to upgrading my system fails currently as the old libmimalloc2.0 package is still present on my system. Both the old as well as the bumped libmimalloc3 package provide the same libmimalloc.so.3.0 library which dpkg is unhappy about, as can be seen below: Preparing to unpack .../libmimalloc3_3.0.1+ds-2+b1_amd64.deb ... Unpacking libmimalloc3:amd64 (3.0.1+ds-2+b1) ... dpkg: error processing archive /var/cache/apt/archives/libmimalloc3_3.0.1+ds-2+b1_amd64.deb (-- unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libmimalloc.so.3.0', which is also in package libmimalloc2.0:amd64 (3.0.1+ds-1) Errors were encountered while processing: /var/cache/apt/archives/libmimalloc3_3.0.1+ds-2+b1_amd64.deb Error: Sub-process /usr/bin/dpkg returned an error code (1) $ aptitude why libmimalloc2.0 Automatically installed, current version 3.0.1+ds-1, priority optional No dependencies require to install libmimalloc2.0 As no other packages (on my system) depends on libmimalloc2.0 anymore I can safely remove it, but I'm wondering if we're missing a Breaks/Replaces to ensure the old binary packages get removed on upgrade. Actually I'm kinda wondering why piuparts [0] did not complain here... Additionally, I'm not entirely sure whether this bug's severity is set correctly. (And I believe it should actually be "serious", but wanted to err on the safe side). Thank you for your work in mimalloc! -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.6-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
signature.asc
Description: This is a digitally signed message part