[gentoo-amd64] Re: /lib32/* missing after system upgrade

[Duncan <1i5t5.duncan@cox.net>]

"Ryan Sims" <rwsims@gmail.com> posted
64e8d2f20701091515i6fc1b696o6ae8ad6140593b9f@mail.gmail.com, excerpted
below, on  Tue, 09 Jan 2007 18:15:50 -0500:

> On 1/9/07, Harm Geerts <harmgeerts@home.nl> wrote:
>> On Tuesday 09 January 2007 17:20, Ryan Sims wrote:
>> > On 1/9/07, Piotr Jaroszyński <peper@gentoo.org> wrote:
>> > > On Tuesday 09 January 2007 16:27, Einar S. Idsø wrote:
>> > > > Some further info: I just remembered that I also changed the
>> > > > symlink for /etc/make.profile. For some reason I changed it to
>> > > > point to /usr/portage/profiles/default-linux/x86/2006.0, which
>> > > > doesn't seem right... I suppose I should rather have used
>> > > > /usr/portage/profiles/default-linux/amd64/2006.1/(desktop|server)?
>> > > >
>> > > > Did I just stupidly break my system?
>> > >
>> > > You have switched to non-multilib profile... Switch it back asap and
>> > > reemerge whatever you emerged on invalid profile.
>> >
>> > Is that possible?
>> >
>> > from http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#multilib :
>> > "Currently you cannot switch from a no-multilib to a multilib-enabled
>> > profile, so think over your decision twice before you use the
>> > no-multilib profile."
>>
>> The reason it's not possible is because it breaks the system. portage
>> does not prevent you from changing to an incompatible profile.
> 
> Understood, I was thinking of "Switch it back asap and reemerge" as
> impossible.  I have a deep respect for portage, but I absolutely do not
> expect it to protect me from myself ;)

In theory, the only big damage is likely to be the toolchain,
glibc/gcc/binutils/sandbox.  Of course, with those damaged, getting stuff
working again is going to be "interesting" to say the least.  However, one
should be able to recover by resetting the profile correctly, then using
quickpkg on the toolchain packages out of an amd64 stage-X install, and
merging those binary packages directly over the fubar-ed system.  That
should recover a working toolchain, after which one would of course emerge
--emptytree --deep --update world, to finish the recovery.

If you've been running FEATURES=buildpkg for some time before the screwup,
and caught the problem early enough (or you can use another amd64 machine
as here), you can remerge anything that wasn't merged on the bad profile
(thus overwriting the last good binpkgs) from the binpkgs.

-- 
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@gentoo.org mailing list