From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1H4w8L-0005gW-Vz for garchives@archives.gentoo.org; Thu, 11 Jan 2007 09:22:06 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0B9KEc2029724; Thu, 11 Jan 2007 09:20:14 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id l0B9KEuH014239 for ; Thu, 11 Jan 2007 09:20:14 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H4w6T-0004Oy-2N for gentoo-amd64@lists.gentoo.org; Thu, 11 Jan 2007 10:20:09 +0100 Received: from ip68-231-13-122.ph.ph.cox.net ([68.231.13.122]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Jan 2007 10:20:09 +0100 Received: from 1i5t5.duncan by ip68-231-13-122.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Jan 2007 10:20:09 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: /lib32/* missing after system upgrade Date: Thu, 11 Jan 2007 09:19:56 +0000 (UTC) Message-ID: References: <45A3B0C3.3040904@itk.ntnu.no> <200701091713.23427.peper@gentoo.org> <64e8d2f20701090820s4921cf2dl27ef385083d1001f@mail.gmail.com> <200701092141.26431.harmgeerts@home.nl> <64e8d2f20701091515i6fc1b696o6ae8ad6140593b9f@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-13-122.ph.ph.cox.net User-Agent: pan 0.120 (Plate of Shrimp) Sender: news Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id l0B9KEcx029724 X-Archives-Salt: 5a5bda65-b911-4392-859a-59dd8d0c2c7e X-Archives-Hash: 42948bc2de4ec26a74f109e6262f491f "Ryan Sims" posted 64e8d2f20701091515i6fc1b696o6ae8ad6140593b9f@mail.gmail.com, excerpted below, on Tue, 09 Jan 2007 18:15:50 -0500: > On 1/9/07, Harm Geerts wrote: >> On Tuesday 09 January 2007 17:20, Ryan Sims wrote: >> > On 1/9/07, Piotr Jaroszy=C5=84ski wrote: >> > > On Tuesday 09 January 2007 16:27, Einar S. Ids=C3=B8 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 a= nd >> > > 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-enable= d >> > 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. >=20 > 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, on= e 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 emerg= e --emptytree --deep --update world, to finish the recovery. If you've been running FEATURES=3Dbuildpkg for some time before the screw= up, 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. --=20 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 --=20 gentoo-amd64@gentoo.org mailing list