glibc 2.31 on -current: any horror stories or surprises?
by gus3 from LinuxQuestions.org on (#4YXNR)
Normally, when a glibc update appears in -current, I don't mind taking the plunge on a spare laptop. But this time, PatV left it in -testing, which gives me pause.
I don't see any threads open for this particular matter, so I'm asking it now. Has anyone running -current encountered a reason NOT to upgrade to glibc-2.31?
I don't see any threads open for this particular matter, so I'm asking it now. Has anyone running -current encountered a reason NOT to upgrade to glibc-2.31?