Nikos Chantziaras schrieb:
>
> 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 didn't consider those packages as critical (gcc was *not* built
after the glibc upgrade!), so I succeeded to downgrade glibc at last.
But now "emerge -1 apache" doesn't work because "patch" is needed,
and "patch" is still looking for glibc 2.28. And "emerge -1 patch"
seems to need the new glibc anyway:
* patch-2.7.6.tar.xz BLAKE2B SHA512 size ;-) ...
[ ok ]
>>> Unpacking source...
>>> Unpacking patch-2.7.6.tar.xz to
>>> /var/tmp/portage/sys-devel/patch-2.7.6-r3/work
>>> Source unpacked in /var/tmp/portage/sys-devel/patch-2.7.6-r3/work
>>> Preparing source in
>>> /var/tmp/portage/sys-devel/patch-2.7.6-r3/work/patch-2.7.6 ...
* Applying patch-2.7.6-fix-test-suite.patch ...
patch: /lib/libc.so.6: version `GLIBC_2.28' not found (required by patch)
[ !! ]
* ERROR: sys-devel/patch-2.7.6-r3::gentoo failed (prepare phase):
* patch -p1 failed with
/var/tmp/portage/sys-devel/patch-2.7.6-r3/files/patch-2.7.6-fix-test-suite.patch
So it seems that I cannot emerge "patch" because I need to patch
"patch" :-( Am I stuck now??? What to do??
-Matt
