re-sending this as the ML bounced my initial email from scho...@ubuntu.com,initially sent yesterday. The observant among you will have noticed that it was indeed uploaded.
************ Hello there! This announcement usually comes in a bit earlier in the cycle, but stars didn't align properly this time. Better late than never, I suppose. Later today, I will be uploading a new upstream version of glibc. There was *no* glibc-specific test rebuild this time around, partly due to other fun things happening in the archive. Sadly, besides the usual clogging of the queues, I do expect a bit of disruption, as basically any new build of packages that uses cfsetspeed() or its cousins will pick up its new ABI and will be stuck behind glibc for proposed migration. For reference, codesearch.d.n gives me 5218 hits, so I'm expecting a few packages will be caught by this. The regex you want to use to search your code is `cf[sg]et[io]%3Fspeed`. Beyond this, I do *not* expect major breakage. The full upstream changelog is available at [0], I encourage you to browse it for some of the new features. Now, if I'm wrong about lack of major breakage, you want to watch out for the following symptoms in your autopkgtests, build logs, or bug reports: * FTBFS due to missing termio.h Your package is using some really outdated interfaces that were already obsolete when the Berlin Wall fell. Please look into termios.h. * ARM issues only on modern ARM64 processors (e.g. Apple M4), around coroutine or exception-handling code. Tobias, do we even support running on M4 hardware!? Cheers, Simon [0]: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=glibc-2.42 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
