Greetings. I've just uploaded gettext 0.23.1-0.1 for experimental.
[ This is preliminary, don't worry for the changelog, there will be a proper one in unstable. Also please don't close any bugs yet, I want to close them in unstable ]. There is a list of upstream changes here: https://savannah.gnu.org/news/?id=10699 I've built the whole archive with the new gettext and I know that the number of packages which FTBFS is approximately 22 (originally 24 but I already fixed two of them). In most cases, the failure is like this: make[3]: Entering directory '/<<PKGBUILDDIR>>/po' *** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.20 but the autoconf macros are from gettext version 0.22 and I expect that the trick I used for sitecopy (QA maintained), which is to copy Makefile.in.in *after* dh_autoreconf: https://salsa.debian.org/debian/sitecopy/-/commit/27e4ed4205b7c62197f0428b6890d7bac2f5692e will also work in many other cases. My plan is to report those bugs with severity:important now and then wait a week before uploading gettext for unstable (at which time the remaining bugs would be RC). Would the Release Managers approve this? Thanks.
