The failure is in a gnulib test. I've bisected it to the following glibc upstream commit:
https://sourceware.org/git/?p=glibc.git;a=commit;h=642933158e7cf072d873231b1a9bb03291f2b989 The issue has been reported upstream. ** Bug watch added: Sourceware.org Bugzilla #30065 https://sourceware.org/bugzilla/show_bug.cgi?id=30065 ** Also affects: libunistring via https://sourceware.org/bugzilla/show_bug.cgi?id=30065 Importance: Unknown Status: Unknown ** Project changed: libunistring => glibc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/2004264 Title: FTBFS against glibc 2.37 Status in GLibC: Unknown Status in libunistring package in Ubuntu: New Bug description: Hi, During a mass rebuild of Lunar, the package libunistring failed to build against a snapshot of the upcoming glibc 2.37, while building fine using 2.36 as present in the archive. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz I was able to reproduce this when building against my latest snapshot (done this morning), published in this PPA: https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages The failing tests appear to be test-strncat and test-u8-strncat. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/2004264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
