Re: [gentoo-amd64] Re: Recovering from emerge --prune

[Jonathan Schaeffer]

Thanks for the complete answer Duncan, there is matter to try things
out. I think I'll learn a lot in recovering my system :)

I'll try those things out and if I'm unlucky, I'll consider
reinstalling from scratch.

2006/5/16, Duncan <1i5t5.duncan@×××.net>:
> "Jonathan Schaeffer" <joschaeffer@×××××.com> posted
> d60596f50605152339u5a5173c6s7659c73403a95308@××××××××××.com, excerpted
> below, on  Tue, 16 May 2006 08:39:10 +0200:
>
> > just for improving my knowledge of the Gentoo system, I tried out the
> > emerge -P option (... well one would say reading the man page is a
> > good way to learn too)
>
> Yeah... that's a mistake I don't believe you'll do again!  How many times
> does it have to be said, use --pretend on any emerge operation,
> PARTICULARLY when unmerging, and check for sanity before actually doing it!?
>
> Hopefully, your post averts someone else's mistake.  =8^)
>
> > Allwright, the system is broken but it seems that it is recoverable.
> > emerge -uDN world will recompile the libraries I've lost.
>
> Right.  Of course, if you were using FEATURES=buildpkg, you'd have binary
> versions of everything, so it'd likely be a matter of half an hour's work
> to remerge them.  Features=buildpkg is my favorite under-publicised portage
> feature! =8^)  It's saved my butt several times, now!  You may wish to
> read up on it right away, and consider turning it on before you start
> rebuilding things.  That'll give you a head-start at getting all your
> packages backed up in binary package format, and you'll be better prepared
> the next time something goes wrong.  (If you are worried about space,
> you'll need 2 gig minimum for binary copies of all packages in a full
> desktop system.  It won't take quite that much, but you do want to be able
> to upgrade stuff and have both copies on hand for awhile, in case you need
> to revert to the old version.  4 gigs is better -- you won't  have to
> clean out old packages as often.)
>
> > While doing this, an error occured in emerging grub. This is what
> > shows up in the config.log
>
> Unfortunately, I can't help you there.  I might be able to trial and error
> my way thru fixing it if it occurred here, but I see anything I'm familiar
> enough with to dare trying to explain.
>
> One thing you might try... emerge grub-static for the time being.  That's
> a binary no-compile version.  If you want the self-compiled one later, try
> grub again, after everything else is merged.  That might well cure the
> problem, and is what I'd try in that situation.
>
> Also... note that grub is 32-bit.  It's possible your 32-bit side isn't
> set up quite right, while the 64-bit side is still working fine.  I've had
> that happen a couple times.  You may need to get a known-good binary
> package glibc, to bootstrap a working 32-bit glibc, again.  I had to do
> that at one point.  Before you do that, however, try merging it with
> FEATURES=-sandbox.  It's possible your 32-bit sandbox is screwed up, and
> it'll work if you merge without that.  (If you are worried about security,
> try FEATURES=userpriv whenever you turn off sandbox.  It doesn't always
> work and you have to go without both, but sometimes it does.)
>
> Shots in the dark and true, I can't explain how they'd fix the problem
> you reported, but maybe one of them will have gotten lucky and hit whatever
> your problem is.  =8^)
>
>
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
> --
> gentoo-amd64@g.o mailing list
>
>

-- 
gentoo-amd64@g.o mailing list