We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
clang-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
clang-11-doc | 1:11.1.0-6 | all
clang-11-examples | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
clang-format-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
clang-tidy-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
clang-tools-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
clangd-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libc++-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libc++1-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libc++abi-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libc++abi1-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libclang-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libclang-common-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libclang-cpp11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libclang-cpp11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libclang1-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libfuzzer-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
liblld-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
liblld-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
liblldb-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
liblldb-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libllvm-11-ocaml-dev | 1:11.1.0-6+b2 | amd64, arm64, armhf, ppc64el, s390x
libllvm11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libomp-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armhf, i386, mips64el, ppc64el
libomp-11-doc | 1:11.1.0-6+b2 | amd64, arm64, armhf, i386, mips64el, ppc64el
libomp5-11 | 1:11.1.0-6+b2 | amd64, arm64, armhf, i386, mips64el, ppc64el
lld-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
lldb-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
llvm-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
llvm-11-dev | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
llvm-11-doc | 1:11.1.0-6 | all
llvm-11-examples | 1:11.1.0-6 | all
llvm-11-linker-tools | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
llvm-11-runtime | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
llvm-11-tools | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
llvm-toolchain-11 | 1:11.1.0-6 | source
python3-clang-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
python3-lldb-11 | 1:11.1.0-6+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
------------------- Reason -------------------
ROM; Limit the number of llvm versions
----------------------------------------------
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 1000941@bugs.debian.org.
The full log for this bug can be viewed at https://bugs.debian.org/1000941
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
