Hi,

Following the s390 removal, there is cruft left in the archive that dak
can't remove automatically. Therefore please remove the following binary
packages that are no longer built from gcc-15:
- g++-15-multilib
- gcc-15-multilib
- gccgo-15-multilib
- gdc-15-multilib
- gfortran-15-multilib
- gobjc++-15-multilib
- gobjc-15-multilib
- lib32asan8
- lib32atomic1
- lib32gcc-15-dev
- lib32gcc-s1
- lib32gfortran-15-dev
- lib32gfortran5
- lib32go-15-dev
- lib32go24
- lib32gomp1
- lib32gphobos-15-dev
- lib32gphobos6
- lib32itm1
- lib32objc-15-dev
- lib32objc4
- lib32stdc++-15-dev
- lib32stdc++6
- lib32stdc++6-15-dbg
- lib32ubsan1

DAK will likely complain that it breaks build-depends, but they are all
architecture qualified and do not apply to s390x. Therefore please
ignore the build-dependencies issue reported by DAK.

Thanks
Aurelien

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

g++-15-multilib |  15.2.0-12 | s390x
gcc-15-multilib |  15.2.0-12 | s390x
gccgo-15-multilib |  15.2.0-12 | s390x
gdc-15-multilib |  15.2.0-12 | s390x
gfortran-15-multilib |  15.2.0-12 | s390x
gobjc++-15-multilib |  15.2.0-12 | s390x
gobjc-15-multilib |  15.2.0-12 | s390x
lib32asan8 |  15.2.0-12 | s390x
lib32atomic1 |  15.2.0-12 | s390x
lib32gcc-15-dev |  15.2.0-12 | s390x
lib32gcc-s1 |  15.2.0-12 | s390x
lib32gfortran-15-dev |  15.2.0-12 | s390x
lib32gfortran5 |  15.2.0-12 | s390x
lib32go-15-dev |  15.2.0-12 | s390x
 lib32go24 |  15.2.0-12 | s390x
lib32gomp1 |  15.2.0-12 | s390x
lib32gphobos-15-dev |  15.2.0-12 | s390x
lib32gphobos6 |  15.2.0-12 | s390x
 lib32itm1 |  15.2.0-12 | s390x
lib32objc-15-dev |  15.2.0-12 | s390x
lib32objc4 |  15.2.0-12 | s390x
lib32stdc++-15-dev |  15.2.0-12 | s390x
lib32stdc++6 |  15.2.0-12 | s390x
lib32stdc++6-15-dbg |  15.2.0-12 | s390x
lib32ubsan1 |  15.2.0-12 | s390x

------------------- Reason -------------------
NBS; 31-bit s390 removal
----------------------------------------------

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.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1139099@bugs.debian.org.

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

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.
Thorsten Alteholz (the ftpmaster behind the curtain)