Your message dated Wed, 03 Jun 2020 21:55:11 +0000
with message-id <e1jgblr-0009ts...@fasolo.debian.org>
and subject line Bug#947438: Removed package(s) from unstable
has caused the Debian Bug report #947438,
regarding RM: llvm-toolchain-7 -- ROM; Less versions of llvm, the better
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 ow...@bugs.debian.org
immediately.)


-- 
947438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal


Hello,

As we are starting the migration to 9, we should delete -7 now.

 % ssh mirror.ftp-master.debian.org "dak rm -Rn llvm-toolchain-7"

Will remove the following packages from unstable:

clang-7 | 1:7.0.1-9+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
[...]
python-lldb-7 | 1:7.0.1-9+b2 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el

Maintainer: LLVM Packaging Team <pkg-llvm-t...@lists.alioth.debian.org>

------------------- Reason -------------------

----------------------------------------------

Checking reverse dependencies...
# Broken Depends:
aiscm: aiscm [amd64]
bpftrace: bpftrace [amd64 arm64 ppc64el]
flang: flang-7 [amd64 arm64 ppc64el]
       libflang0d-7 [amd64 arm64 ppc64el]
gnat-gps: gnat-gps [amd64 arm64 mips64el ppc64el s390x]
ycmd: ycmd

# Broken Build-Depends:
aiscm: clang-7
       libomp-7-dev
       llvm-7
       llvm-7-dev
beignet: clang-7
         libclang-7-dev
         llvm-7-dev
bpftrace: clang-7
          libclang-7-dev
          llvm-7-dev
flang: libomp-7-dev
       llvm-7
       llvm-7-dev
       llvm-7-tools


I will report the bugs.

Sylvestre

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

   clang-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
clang-7-examples | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
clang-format-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
clang-tidy-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
clang-tools-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
libc++-7-dev | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
 libc++1-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libc++abi-7-dev | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
libc++abi1-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libclang-7-dev | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
libclang-common-7-dev | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
libclang1-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libfuzzer-7-dev | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
  liblld-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
liblld-7-dev | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
 liblldb-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
liblldb-7-dev | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el
libllvm-7-ocaml-dev | 1:7.0.1-12 | amd64, arm64, armhf, i386, ppc64el, s390x
  libllvm7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
libomp-7-dev | 1:7.0.1-12 | amd64, arm64, armhf, i386, mips64el, ppc64el
 libomp5-7 | 1:7.0.1-12 | amd64, arm64, armhf, i386, mips64el, ppc64el
     lld-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
    lldb-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el
    llvm-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
llvm-7-dev | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
llvm-7-examples | 1:7.0.1-12 | all
llvm-7-runtime | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
llvm-7-tools | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
llvm-toolchain-7 | 1:7.0.1-12 | source
python-clang-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
python-lldb-7 | 1:7.0.1-12 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el

------------------- Reason -------------------
ROM; Less versions of llvm, the better
----------------------------------------------

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 947...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/947438

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to