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 <vincent@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)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Thu, 25 Jan 2024 14:57:23 +0000
with message-id <E1rT1AR-003lvi-Tr@fasolo.debian.org>
and subject line Bug#1061438: fixed in tpm2-tss 4.0.1-7
has caused the Debian Bug report #1061438,
regarding tpm2-tss: can't upgrade the tpm2-tss packages to 4.0.1-6; missing Conflicts?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


--
1061438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061438
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 24 Jan 2024 14:20:15 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-3.9 required=4.0 tests=BAYES_00,FOURLA,SPF_HELO_NONE,
SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 20; hammy, 150; neutral, 119; spammy,
0. spammytokens: hammytokens:0.000-+--trixie,
0.000-+--H*F:D*vinc17.net, 0.000-+--H*rp:D*vinc17.net, 0.000-+--cutf8,
0.000-+--CUTF8
Return-path: <vincent@vinc17.net>
Received: from disset.lip.ens-lyon.fr ([140.77.12.53]:53550)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim 4.94.2)
(envelope-from <vincent@vinc17.net>)
id 1rSe6w-006oi8-MJ
fo