Hello! On Tue, Aug 8, 2023 at 8:16 PM Samuel Thibault <samuel.thiba...@gnu.org> wrote: > Hello, > > I continued stabbing at the network issue, it was just a size alignment > problem, so that depending on their sizes, half of the network packets > would be discarded by mach_msg. Hurd-amd64 packages are getting rebuilt > to contain the fix.
Awesome! > The issue I'm still seeing now is that I cannot get to install some > packages, such as libicu72. When I pass it as extra package to > debootstrap, it does get installed, but when I "dpkg -i" it by hand, > things halt. > > And there is still the 64bit change proposed proposed by Flavio that > needs to get reviewed. There's another issue we need to sort out: is it OK for Debian to ship glibc 2.36 whose symbols claim to be GLIBC_2.38? It doesn't look like there's been any compat symbols (as in SHLIB_COMPAT / compat_symbol) added in between, but programs built against actual glibc 2.38 link against newer symbols that just aren't present in 2.36 (such as those __isoc23 functions), and you get symbol errors at runtime, instead of the usual error about the required version not being present. Could there be other side effects? Sergey
