Hello.
A bug affects the Ada tests during the build of the gcc-12 source
package.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066052
Such error messages happen on each (uncoordinated) change in the sources
of an Ada library. Some sources for the standard library built by GCC
are generated from C headers, so, as Matthias wrote in the bug report,
this is without doubt caused by the t64 transition (especially taking
into account that Ada.Calendar defines types for time representation).
All/most Ada packages will probably soon FTBFS with a similar message.
All/most Ada libraries need small manual changes and a passage through
NEW in order to fix this (Ada -dev packages built with gcc-12 and
earlier carry a version, in addition to the SO version carried by
library packages).
I agree with Matthias that we should instead start the gcc-13 transition
in unstable. All packages are ready in experimental, with all library
packages already renamed through NEW. But unfortunately also with
intrusive unrelated changes, for example new upstream versions and a new
Ada workflow removing the version from -dev package names.
This will fix the issue quickly (only a new changelog entry for each
package), but I would like a formal approval by the release managers
before starting the gnat-13 transition.
As described above in #1065309, all precautions have been taken in
experimental, and all is needed is a rebuild in unstable with a new
changelog entry. The FTBFSs in experimental reported by the salsa CI
pipeline can be ignored, they are caused by the difficulty to resolve
build dependencies in a context mixing unstable and experimental.
For the record, some unrelated changes in the gnat-12 sources were
already causing similar bugs (#1061631, [1]#1061633, [2]#1064745 [3]),
that will also be fixed by the gnat-13 transition. These bugs are less
important because they affect a few Ada packages, not GCC.
Links:
------
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061631
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061633
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064745