> On the Debian side, there is no huge urgency about this bug. glibc 2.43 > got uploaded to experimental a few days ago, and at this stage I am just > trying to get a first status by looking at debci, and filling bugs as I > find them. It will take a few weeks before this glibc version gets ready > for unstable.
I actually expect them to release m4 1.4.21 soon, because I tried the patch they provided and it does not fix all the failures, apparently gnulib has evolved too much since the last m4 was released. I see that the new glibc also breaks gettext 0.26, so we will have to keep 0.23.2 in unstable for some more time until I have a fix (I have not had time to check gettext 1.0 yet). Maintainers will have some more time to fix the 32 broken packages I found. Thanks.
