Bug#1038820: transition: glibc 2.37

[Aurelien Jarno <aurel32@debian.org>]

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: debian-glibc@lists.debian.org
Control: affects -1 + src:glibc

Dear release team,

I would like to get a transition slot for glibc 2.37. It has been
available in experimental for a bit more than a month and does not have
any known issue. It has been built successfully on all release
architectures and many ports architectures (technically 2.37-2 hasn't
been built yet on mipsel and mips64el due to the buildds lagging, but
2.37-1 has been built successfully).

As glibc is using symbol versioning, there is no soname change. That
said a few packages are using libc internal symbols and have to be
rebuilt for this transition. Here is the corresponding ben file:

  title = "glibc";
  is_affected = .depends ~ /libc[0-9.]* \(<</;
  is_good = .depends ~ /libc[0-9.]* \(<< 2.38\)/;
  is_bad = .depends ~ /libc[0-9.]* \(<< 2.37\)/;

Only a single symbol has been added to 32-bit architectures using non
64-bit time_t (i.e. for release architectures: armel armhf mipsel). This
symbol is only used when building packages with -D_TIME_BITS=64, so its
usage is very limited. 64-bit architectures do not have new symbols.
Therefore it's very unlikely that glibc 2.37 blocks the migration of
other packages to testing during the transition. 

Thanks for considering.

Regards,
Aurelien