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

    cpp-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
    g++-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
g++-10-multilib |   10.5.0-4 | amd64, i386, mips64el, s390x
    gcc-10 |   10.5.0-4 | source, amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
gcc-10-base |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
gcc-10-hppa64-linux-gnu |   10.5.0-4 | amd64, i386
gcc-10-locales |   10.5.0-4 | all
gcc-10-multilib |   10.5.0-4 | amd64, i386, mips64el, s390x
gcc-10-offload-nvptx |   10.5.0-4 | amd64, ppc64el
gcc-10-plugin-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
gcc-10-source |   10.5.0-4 | all
gcc-10-test-results |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
gccbrig-10 |   10.5.0-4 | amd64, i386
  gccgo-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
gccgo-10-multilib |   10.5.0-4 | amd64, i386, mips64el, s390x
    gdc-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
gdc-10-multilib |   10.5.0-4 | amd64, i386, mips64el, s390x
gfortran-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
gfortran-10-multilib |   10.5.0-4 | amd64, i386, mips64el, s390x
    gm2-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
   gnat-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
gobjc++-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
gobjc++-10-multilib |   10.5.0-4 | amd64, i386, mips64el, s390x
  gobjc-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
gobjc-10-multilib |   10.5.0-4 | amd64, i386, mips64el, s390x
lib32gcc-10-dev |   10.5.0-4 | amd64, mips64el, s390x
lib32gfortran-10-dev |   10.5.0-4 | amd64, mips64el, s390x
lib32go-10-dev |   10.5.0-4 | amd64, mips64el, s390x
 lib32go16 |   10.5.0-4 | amd64, mips64el, s390x
lib32gphobos-10-dev |   10.5.0-4 | amd64, mips64el, s390x
lib32gphobos1 |   10.5.0-4 | amd64, mips64el, s390x
lib32objc-10-dev |   10.5.0-4 | amd64, mips64el, s390x
lib32stdc++-10-dev |   10.5.0-4 | amd64, mips64el, s390x
lib32stdc++6-10-dbg |   10.5.0-4 | amd64, mips64el, s390x
lib64gcc-10-dev |   10.5.0-4 | i386
lib64gfortran-10-dev |   10.5.0-4 | i386
lib64go-10-dev |   10.5.0-4 | i386
 lib64go16 |   10.5.0-4 | i386
lib64gphobos-10-dev |   10.5.0-4 | i386
lib64gphobos1 |   10.5.0-4 | i386
lib64objc-10-dev |   10.5.0-4 | i386
lib64stdc++-10-dev |   10.5.0-4 | i386
lib64stdc++6-10-dbg |   10.5.0-4 | i386
libgcc-10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libgccjit-10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libgccjit-10-doc |   10.5.0-4 | all
libgfortran-10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libgm2-10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
 libgm2-15 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
libgnat-10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
libgnat-util10 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libgnat-util10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libgo-10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
   libgo16 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
libgomp-plugin-hsa1 |   10.5.0-4 | amd64
libgphobos-10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libgphobos1 |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, 
s390x
libhsail-rt-10-dev |   10.5.0-4 | amd64, i386
libn32gcc-10-dev |   10.5.0-4 | mips64el
libn32gfortran-10-dev |   10.5.0-4 | mips64el
libn32go-10-dev |   10.5.0-4 | mips64el
libn32go16 |   10.5.0-4 | mips64el
libn32gphobos-10-dev |   10.5.0-4 | mips64el
libn32gphobos1 |   10.5.0-4 | mips64el
libn32objc-10-dev |   10.5.0-4 | mips64el
libn32stdc++-10-dev |   10.5.0-4 | mips64el
libn32stdc++6-10-dbg |   10.5.0-4 | mips64el
libobjc-10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libstdc++-10-dev |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libstdc++-10-doc |   10.5.0-4 | all
libstdc++-10-pic |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libstdc++6-10-dbg |   10.5.0-4 | amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, s390x
libx32gcc-10-dev |   10.5.0-4 | amd64, i386
libx32gfortran-10-dev |   10.5.0-4 | amd64, i386
libx32go-10-dev |   10.5.0-4 | amd64, i386
libx32go16 |   10.5.0-4 | amd64, i386
libx32gphobos-10-dev |   10.5.0-4 | amd64, i386
libx32gphobos1 |   10.5.0-4 | amd64, i386
libx32objc-10-dev |   10.5.0-4 | amd64, i386
libx32stdc++-10-dev |   10.5.0-4 | amd64, i386
libx32stdc++6-10-dbg |   10.5.0-4 | amd64, i386

------------------- Reason -------------------
ROM: gcc-10-*, superseded by newer 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 1076...@bugs.debian.org.

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

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)

Reply via email to