m: /lib/libc.so.6: version `GLIBC_2.4' not found (required by rm) >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking udev-087.tar.bz2 ;-) install: /lib/libc.so.6: version `GLIBC_2.4' not found (required by install) !!! ERROR: sys-fs/udev-087-r1 failed. not a whole lot works, for example: [root@kronos shaw 519]% mkdir /var/tmp/portage/udev-087-r1/work mkdir: /lib/libc.so.6: version `GLIBC_2.4' not found (required by mkdir) I did a emerge -Dup prior to the emerge but it didn't say anything would be downgraded or removed. emerge --search glibc shows that 2.3.6-r3 is installed, with that being the latest version available. Note that I'm running running an AMD64 machine.
Reopen with emerge --info and 'genlop -s glibc' output (emerge app-portage/genlop if you haven't yet).
Well, the above probably won't work. Try 'mv /bin/grep grep.bak; cp /bin/busybox grep; grep glibc /var/log/emerge.log' and post the output.
emerge, mv, cp won't work. grep does work, however. [shaw@kronos ~ 52]% grep glibc /var/log/emerge.log 1144014567: >>> emerge (24 of 62) sys-libs/glibc-2.3.5-r2 to / 1144014567: === (24 of 62) Cleaning (sys-libs/glibc-2.3.5-r2::/usr/portage/sys-libs/glibc/glibc-2.3.5-r2.ebuild) 1144014568: === (24 of 62) Compiling/Merging (sys-libs/glibc-2.3.5-r2::/usr/portage/sys-libs/glibc/glibc-2.3.5-r2.ebuild) 1144016456: === (24 of 62) Post-Build Cleaning (sys-libs/glibc-2.3.5-r2::/usr/portage/sys-libs/glibc/glibc-2.3.5-r2.ebuild) 1144016458: >>> AUTOCLEAN: sys-libs/glibc 1144016458: ::: completed emerge (24 of 62) sys-libs/glibc-2.3.5-r2 to / 1146341336: *** emerge search glibc 1146341958: *** emerge glibc 1146341958: >>> emerge (1 of 1) sys-libs/glibc-2.3.5-r2 to / 1146341958: === (1 of 1) Cleaning (sys-libs/glibc-2.3.5-r2::/usr/portage/sys-libs/glibc/glibc-2.3.5-r2.ebuild) 1146341959: === (1 of 1) Compiling/Merging (sys-libs/glibc-2.3.5-r2::/usr/portage/sys-libs/glibc/glibc-2.3.5-r2.ebuild) 1146341999: *** emerge glibc-2.4-r1 1146342008: *** emerge =glibc-2.4-r1 1146342015: *** emerge glibc 1146342016: >>> emerge (1 of 1) sys-libs/glibc-2.3.5-r2 to / 1146342016: === (1 of 1) Cleaning (sys-libs/glibc-2.3.5-r2::/usr/portage/sys-libs/glibc/glibc-2.3.5-r2.ebuild) 1146342016: === (1 of 1) Compiling/Merging (sys-libs/glibc-2.3.5-r2::/usr/portage/sys-libs/glibc/glibc-2.3.5-r2.ebuild) 1146343861: === (1 of 1) Post-Build Cleaning (sys-libs/glibc-2.3.5-r2::/usr/portage/sys-libs/glibc/glibc-2.3.5-r2.ebuild) 1146343862: >>> AUTOCLEAN: sys-libs/glibc 1146343862: ::: completed emerge (1 of 1) sys-libs/glibc-2.3.5-r2 to / 1146345751: *** emerge glibc 1146345772: >>> emerge (2 of 2) sys-libs/glibc-2.4-r1 to / 1146345772: === (2 of 2) Cleaning (sys-libs/glibc-2.4-r1::/usr/portage/sys-libs/glibc/glibc-2.4-r1.ebuild) 1146345772: === (2 of 2) Compiling/Merging (sys-libs/glibc-2.4-r1::/usr/portage/sys-libs/glibc/glibc-2.4-r1.ebuild) 1146345811: *** emerge search glibc 1146348734: === (2 of 2) Post-Build Cleaning (sys-libs/glibc-2.4-r1::/usr/portage/sys-libs/glibc/glibc-2.4-r1.ebuild) 1146348736: >>> AUTOCLEAN: sys-libs/glibc 1146348741: === Unmerging... (sys-libs/glibc-2.3.5-r2) 1146348743: >>> unmerge success: sys-libs/glibc-2.3.5-r2 1146348743: ::: completed emerge (2 of 2) sys-libs/glibc-2.4-r1 to / 1150907429: >>> emerge (5 of 12) sys-libs/glibc-2.3.6-r3 to / 1150907429: === (5 of 12) Cleaning (sys-libs/glibc-2.3.6-r3::/usr/portage/sys-libs/glibc/glibc-2.3.6-r3.ebuild) 1150907429: === (5 of 12) Compiling/Merging (sys-libs/glibc-2.3.6-r3::/usr/portage/sys-libs/glibc/glibc-2.3.6-r3.ebuild) 1150910058: >>> AUTOCLEAN: sys-libs/glibc 1150910063: === Unmerging... (sys-libs/glibc-2.4-r1) 1150910068: >>> unmerge success: sys-libs/glibc-2.4-r1 1150910068: === (5 of 12) Post-Build Cleaning (sys-libs/glibc-2.3.6-r3::/usr/portage/sys-libs/glibc/glibc-2.3.6-r3.ebuild) 1150910068: ::: completed emerge (5 of 12) sys-libs/glibc-2.3.6-r3 to / 1150942744: *** emerge search glibc 1150943326: *** emerge search glibc [shaw@kronos ~ 53]%
Well - what could I say. *NEVER* downgrade glibc.
Closing CANTFIX, nothing we could do here. Maybe you could recover this if you manage to get glibc-2.4 binary package and untar it on your system.
I'd guess this happened months ago when I when from ~x86 down to stable, but not sure, I know I had complications doing that. Not sure why it happened during this relatively simple update, but I guess it was a ticking time bomb. I can restore my machine from backup before this latest emerge.. This will put me in a workable state, though I'm not really sure what that state is. Are those timestamps on the output below?
(In reply to comment #6) > Are those timestamps on the output below? Yeah...
Can you tell me when all of this happened? Are those seconds?!
(In reply to comment #8) > Can you tell me when all of this happened? Are those seconds?! 1150907429: >>> emerge (5 of 12) sys-libs/glibc-2.3.6-r3 to / 1150907429: === (5 of 12) Cleaning Wed, 21 Jun 2006 16:30:29 GMT
>In reply to comment #8) > Can you tell me when all of this happened? Are those seconds?! >1150907429: >>> emerge (5 of 12) sys-libs/glibc-2.3.6-r3 to / >1150907429: === (5 of 12) Cleaning >Wed, 21 Jun 2006 16:30:29 GMT Well, this makes sense, because everything worked fine until I did an emerge -Du. Afterwards my system was borked. I did not remove glibc myself, emerge did it itself for reasons that are beyond me. So why did emerge do this?
Please, don't reopen this bug. You've clearly downgraded your glibc from 2.4 to 2.3.6, that's not a Gentoo bug and I've already explained to you that we can't fix your broken system.
(In reply to comment #10) > > Well, this makes sense, because everything worked fine until I did an emerge > -Du. Afterwards my system was borked. I did not remove glibc myself, emerge > did it itself for reasons that are beyond me. > > So why did emerge do this? Your glibc was not removed, it was downgraded. Emerge did this because you can't have two glibc versions installed, that's pretty normal, expected and not a bug either. Closing.
Yes, running emerge -Du clearly unmerged glibc. How is that my fault?
(In reply to comment #13) > Yes, running emerge -Du clearly unmerged glibc. How is that my fault? Erm, most likely when you downgraded from ~x86 to x86, like you yourself said... :P Closed case, nothing we could do here. Next time watch what you are doing to avoid such b0rkage.
emerge -Dup didn't tell me about the downgrade or I would have consulted you guys first.
Last question, promise. My backup is a week or so old and took place long after I went from ~x86 to the stable branch. I'd like to restore from that backup and fix the problem (more than one glibc) somehow that led to emerge downgrading to glibc. Do you think something like that will work or should I just reinstall the box from scratch? The end goal would be to have a system that doesn't get killed when I do a simple emerge. Thanks.
forums.gentoo.org, or #gentoo on IRC. Bugzilla is not a support forum.
