On 13/04/2019 15:20, Matthias Hanft wrote:
Now "admin-panic" is heavily arising. HELP! What can I do??
See which packages were built against the new glib. Do:
$ qlop -l -d 2days
See which packages were emerged AFTER glibc 2.28. Are they critical
packages? If not, downgrade glibc anyway. Then rebuild those packages.
I forgot how to downgrade glibc though :-/
Years ago, this happened to me. After than, I *NEVER* allow new versions
of glibc to be emerged together with other packages. I always exclude
it, let everything else update, then I make a binary package of glibc
(quickpkg glibc) and only then do I emerge the new glibc so I can
downgrade again from the binary package (but again, I forgot how to do
that now...)
