[gentoo-user] glibc completed screwed my system

[gentoo-user] glibc completed screwed my system

[David Grant]

Here's what I did:

I have sticking with gcc-3.x for now... I wanted to upgraded glibc to
2.4. I upgraded it and at the end of the emerge I got this error
similar to this one, mine involved libresolv:

http://forums.gentoo.org/viewtopic-t-443051-postdays-0-postorder-asc-highlight-libresolv+glibc-start-0.html

I then did emerge -C =glibc-2.4-r4 to remove glibc-2.4 completely and
leave 2.3. Now my whole system is b0rked. I can't even chroot in
because it can't run /bin/sh or /bin/bash on the new system. Basically
all binaries are screwed on the new system.

I do have a quickpkg of glibc2.3 but I'm not sure what good that will do.

If anyone can help me I'm desperate to save this system and not have
to reinstall.

-- 
David Grant
http://www.davidgrant.ca
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: glibc completed screwed my system

[David Grant]

A very small step in the right direction...I unzipped the quickpkg I
made into the /mnt/gentoo and now I am able to chroot in there. If I
try to re-emerge glibc-2.3.6 though it complains that "downgrading" is
a sure way to destruction. I'm pretty sure it would be safe for me to
downgrade because I didn't really do much of anything after installing
2.4 so I'm not sure what the problem would be.  The problem is that it
still think 2.4 is installed.

Ah, here we go. emerge -C =glibc-2.4* worked fully this time (it
didn't work fully before, which I forgot to mention). Now it will let
me re-emerge =glibc-2.3* overtop of the quickpkg that I unpacked. I am
also not compiling with nptlonly (which came in to my profile through
2006.1), so it is now emerging with the exact same use flags that it
was before (and the same as what the quickpkg is made from). So
hopefully everything will be cool and I will be able to reboot into
this machine (I couldn't even boot into it after this b0rking
happend).

Dave

On 9/1/06, David Grant <davidgrant@gmail.com> wrote:
> Here's what I did:
>
> I have sticking with gcc-3.x for now... I wanted to upgraded glibc to
> 2.4. I upgraded it and at the end of the emerge I got this error
> similar to this one, mine involved libresolv:
>
> http://forums.gentoo.org/viewtopic-t-443051-postdays-0-postorder-asc-highlight-libresolv+glibc-start-0.html
>
> I then did emerge -C =glibc-2.4-r4 to remove glibc-2.4 completely and
> leave 2.3. Now my whole system is b0rked. I can't even chroot in
> because it can't run /bin/sh or /bin/bash on the new system. Basically
> all binaries are screwed on the new system.
>
> I do have a quickpkg of glibc2.3 but I'm not sure what good that will do.
>
> If anyone can help me I'm desperate to save this system and not have
> to reinstall.
>
> --
> David Grant
> http://www.davidgrant.ca
>


-- 
David Grant
http://www.davidgrant.ca
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: glibc completed screwed my system

[James]

David Grant <davidgrant <at> gmail.com> writes:


> > If anyone can help me I'm desperate to save this system and not have
> > to reinstall.


Well, I have lost xwindows/kde on (2) systems because of an upgrade of
make.profile to point to 2006.1. I'm sure glibc was part of the problem.

A third syxtem, an amd64,  sits just slobering and drooling about;
it will not even allow ls or cat to run.....
so I'm not so sure this one can be saved without a re-installation.

It'd sure been nice if there was a little bit more detail on this,
problem and recovery options. I've googled for links that help, but found
nothing.

So how is the new 2006.1 liveCD working these days?  I'm soon to find
out, on at least one system, maybe (3), 

Any ideas on recovery mechanisms,  for this make.profile/glibc 
problem are most welcome......

I think I'll just drink (quite a lot) and read this list to see how
the smarter half of this list dance around these pending upgrades.
I'm quite sure it's my fault, I just do not have the fortitude
to fight through another twisted hack-fest of a weekend. 

Besides it's labor_day weekend and this is one wage-slave
that is feeling throughly defeated..... My solution is to drink
enough that my singing actually starts to sound acceptable....

ymmv: (Tequila!)
cheers!

James



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: glibc completed screwed my system

[David Grant]

On 9/1/06, James <wireless@tampabay.rr.com> wrote:
> David Grant <davidgrant <at> gmail.com> writes:
>
>
> > > If anyone can help me I'm desperate to save this system and not have
> > > to reinstall.
>
>
> Well, I have lost xwindows/kde on (2) systems because of an upgrade of
> make.profile to point to 2006.1. I'm sure glibc was part of the problem.
>
> A third syxtem, an amd64,  sits just slobering and drooling about;
> it will not even allow ls or cat to run.....
> so I'm not so sure this one can be saved without a re-installation.
>
> It'd sure been nice if there was a little bit more detail on this,
> problem and recovery options. I've googled for links that help, but found
> nothing.
>
> So how is the new 2006.1 liveCD working these days?  I'm soon to find
> out, on at least one system, maybe (3),
>
> Any ideas on recovery mechanisms,  for this make.profile/glibc
> problem are most welcome......
>
> I think I'll just drink (quite a lot) and read this list to see how
> the smarter half of this list dance around these pending upgrades.
> I'm quite sure it's my fault, I just do not have the fortitude
> to fight through another twisted hack-fest of a weekend.

Well all I can say is that without my quickpkg I would probably have
been screwed. Although there is still one other thing I could have
done. I could have grabbed a quickpkg of glibc from another box
(although that box has the newest glibc so actually that wouldn't have
worked). It would probably be possible to find someone on the mailing
list with similar hardware and the correct version of glibc that you
want and they could send you the glibc quickpkg'd up for you.

Here is pretty much the bug as I experienced it:
http://bugs.gentoo.org/show_bug.cgi?id=125868

You can see detail there on how I solved it. My system is now fully
working and recovered.

-- 
David Grant
http://www.davidgrant.ca
-- 
gentoo-user@gentoo.org mailing list