Your message dated Mon, 09 Mar 2026 10:44:38 +0000 with message-id <[email protected]> and subject line Bug#1124755: Removed package(s) from unstable has caused the Debian Bug report #1124755, regarding RM: tss2 -- RoQA; outdated version, rc-buggy, not in stable, leaf, upstream changed name 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 [email protected] immediately.) -- 1124755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124755 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ftp.debian.org Severity: normal User: [email protected] Usertags: remove Control: affects -1 src:tss2 X-Debbugs-CC: [email protected] Dear FTP masters, please remove tss2. In #971758 it was discovered that upstream changed the names of both source and binaries. Thus any updates need to go through NEW anyway. The old version we have is orphaned, did not make it into trixie, and there are no r-deps on it. Maybe don't close #971758 when RMing the package, but it can also easily be reopened and/or turned into an ITP bug. Thanks, Chris
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libtss-dev | 1045-3+b2 | amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x libtss0t64 | 1045-3+b2 | amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x tss2 | 1045-3 | source tss2 | 1045-3+b2 | amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x ------------------- Reason ------------------- RoQA; outdated version, rc-buggy, not in stable, leaf, upstream changed name ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected]. The full log for this bug can be viewed at https://bugs.debian.org/1124755 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
