Your message dated Wed, 12 Mar 2025 02:58:40 +0000
with message-id <[email protected]>
and subject line Bug#1085393: Removed package(s) from unstable
has caused the Debian Bug report #1085393,
regarding RM: dogtag-pki -- RoQA; ftbfs, vulnerable, violates /usr-move, 
rc-buggy
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.)


-- 
1085393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085393
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dogtag-pki
Version: 11.2.1-2
Severity: important
User: [email protected]
Usertags: sidremove

Hi,

in addition to automatic removal suggestions, I would like to suggest
removing dogtag-pki from unstable.

It is not part of bookworm nor trixie. It is a non-key leaf package. It
has been last uploaded more than a year ago. It has four distinct RC
bugs, of which one has a patch since at least four months. It also fails
to build from source since at least three months. It has a privilege
escalation vulnerability. It depends on tomcatjss, which is also rc
buggy and cannot be removed, because it has dogtag-pki as sole reverse
dependency.

If you disagree with the removal suggestion, please add a wontfix tag to
this bug. Otherwise, I'll reassign it into a proper removal bug in about
a month.

Helmut

--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

dogtag-pki |   11.2.1-2 | source, all
dogtag-pki-console-theme |   11.2.1-2 | all
dogtag-pki-server-theme |   11.2.1-2 | all
  pki-base |   11.2.1-2 | all
pki-base-java |   11.2.1-2 | all
    pki-ca |   11.2.1-2 | all
pki-console |   11.2.1-2 | all
pki-javadoc |   11.2.1-2 | all
   pki-kra |   11.2.1-2 | all
  pki-ocsp |   11.2.1-2 | all
pki-server |   11.2.1-2 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
pki-server | 11.2.1-2+b1 | riscv64
   pki-tks |   11.2.1-2 | all
 pki-tools |   11.2.1-2 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
 pki-tools | 11.2.1-2+b1 | riscv64
   pki-tps |   11.2.1-2 | all
python3-pki-base |   11.2.1-2 | all

------------------- Reason -------------------
RoQA; ftbfs, vulnerable, violates /usr-move, rc-buggy
----------------------------------------------

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/1085393

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.
Paul Tagliamonte (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to