Source: tpm2-tss Version: 4.0.1-6 Severity: serious It is not possible to upgrade the tpm2-tss packages to 4.0.1-6 with "apt upgrade" or with aptitude (command line or its TUI, without a *manual* dependency resolution):
root@disset:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libtss2-esys-3.0.2-0 libtss2-sys1 libtss2-tcti-cmd0 libtss2-tcti-device0 libtss2-tcti-mssim0 libtss2-tcti-swtpm0 [...] This is apparently due to the rename of libtss2-mu0 to libtss2-mu-4.0.1-0. This latter package has a Breaks+Replaces, but is that sufficient? i.e. isn't Conflicts needed? https://wiki.debian.org/RenamingPackages says "Conflicts should only be used if two packages can never be unpacked at the same time", which is the case for libtss2-mu0 and libtss2-mu-4.0.1-0. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.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 -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
