On Wed, Aug 15, 2018 at 02:34:54PM +0200, Ulf Volmer wrote: > On 15.08.2018 14:02, Reco wrote: > > On Wed, Aug 15, 2018 at 08:33:37AM -0300, Marcelo Lacerda wrote: > > >> but I imagine that a > >> security update to it doesn't actually change anything to libc source code, > >> so why do the two of them always upgrade together? > > > > Today's stable kernel update brought a patched kernel and a 'perf' tool. > > That's it, no libc upgrade. > > package linux-libc-dev has been also updated today.
True. But libc6 (aka GNU libc) was not updated today, and it's the only libc that counts. Reco
