On Sun, Feb 11, 2018 at 12:45:18AM +0100, Chris Marusich wrote: > Danny Milosavljevic <dan...@scratchpost.org> writes: > > > This is only fixed in glibc 2.27 (not in core-updates). > > Should we upgrade glibc in core-updates, then? Or is it better to do it > in the next core-updates cycle, to avoid still more unexpected breakage?
I think we should not update packages deep in the tree unless there is a security patch. What we have now is well tested. Pj. --
