As usual, we'll update glibc in the archive when the new 2.37 will come,
which should happen on Thursday, with my upload hopefully on Friday.
As a direct consequence, the autopkgtest queues will blow up, and most
arch:any packages uploaded after glibc will be stuck waiting for it to
migrate as they'll have picked up the new version symbols.
Looking at the (incomplete) changelog[0] I don't expect too much
breakage. We've done a test rebuilt of the archive back in December[1],
and I was only able to detect one build failure that seemed clearly
glibc-related, which I'm currently investigating[2].
In the mean time, you can use my PPA[3] to test your packages against a
very recent snapshot (with the exception of the armhf architecture which
is currently FTBFS).
Cheers,
Simon
[0]: https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=NEWS;hb=HEAD
[1]: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html
[2]: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/2004264
[3]: https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot
--
Simon Chopin
Foundations Team Ubuntu MOTU/Core Dev
simon.chopin@canonical.com schopin@ubuntu.com
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
