| 1 |
Nikos Chantziaras schrieb: |
| 2 |
> |
| 3 |
> See which packages were built against the new glib. Do: |
| 4 |
> $ qlop -l -d 2days |
| 5 |
> See which packages were emerged AFTER glibc 2.28. Are they critical |
| 6 |
> packages? If not, downgrade glibc anyway. Then rebuild those packages. |
| 7 |
|
| 8 |
I didn't consider those packages as critical (gcc was *not* built |
| 9 |
after the glibc upgrade!), so I succeeded to downgrade glibc at last. |
| 10 |
But now "emerge -1 apache" doesn't work because "patch" is needed, |
| 11 |
and "patch" is still looking for glibc 2.28. And "emerge -1 patch" |
| 12 |
seems to need the new glibc anyway: |
| 13 |
|
| 14 |
* patch-2.7.6.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] |
| 15 |
>>> Unpacking source... |
| 16 |
>>> Unpacking patch-2.7.6.tar.xz to /var/tmp/portage/sys-devel/patch-2.7.6-r3/work |
| 17 |
>>> Source unpacked in /var/tmp/portage/sys-devel/patch-2.7.6-r3/work |
| 18 |
>>> Preparing source in /var/tmp/portage/sys-devel/patch-2.7.6-r3/work/patch-2.7.6 ... |
| 19 |
* Applying patch-2.7.6-fix-test-suite.patch ... |
| 20 |
patch: /lib/libc.so.6: version `GLIBC_2.28' not found (required by patch) [ !! ] |
| 21 |
* ERROR: sys-devel/patch-2.7.6-r3::gentoo failed (prepare phase): |
| 22 |
* patch -p1 failed with /var/tmp/portage/sys-devel/patch-2.7.6-r3/files/patch-2.7.6-fix-test-suite.patch |
| 23 |
|
| 24 |
So it seems that I cannot emerge "patch" because I need to patch |
| 25 |
"patch" :-( Am I stuck now??? What to do?? |
| 26 |
|
| 27 |
-Matt |
Archives