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.60) (envelope-from ) id 1GOH1h-0001FK-U5 for garchives@archives.gentoo.org; Fri, 15 Sep 2006 16:58:54 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8FGvL68024013; Fri, 15 Sep 2006 16:57:21 GMT Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8FGqQTw011746 for ; Fri, 15 Sep 2006 16:52:26 GMT Received: by ug-out-1314.google.com with SMTP id p27so173844ugc for ; Fri, 15 Sep 2006 09:52:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ubtoZKa9nKgziUXXqQwhbghq/ldUWKNtlPGRk8whWKECBwRVA5bv1yEQt+VxQ8GSPpuDVF1n9a97RHHE/DVqU13GuoVvglthYEGB9t6jZhjFlbb+SYUnFdXFZas2g+IFI56xhzcQSnlNm8SupwNuMITt6mXueDp2+BRuGTQUMh0= Received: by 10.66.220.17 with SMTP id s17mr5493327ugg; Fri, 15 Sep 2006 09:52:25 -0700 (PDT) Received: by 10.66.245.16 with HTTP; Fri, 15 Sep 2006 09:52:25 -0700 (PDT) Message-ID: Date: Fri, 15 Sep 2006 09:52:25 -0700 From: "David Grant" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Update to glibc-2.4-r3 with gcc-3.4.6 In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_227006_14702114.1158339145730" References: X-Archives-Salt: 9f9b529c-ce2a-414a-b0fd-c608b74df161 X-Archives-Hash: 3c21178aaa7e6cad2973ba0eafab1c49 ------=_Part_227006_14702114.1158339145730 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 9/15/06, Remy Blank wrote: > > David Grant wrote: > > I did and I totally screwed up my system. I managed to fix it eventually > > by booting to a live CD and untaring the quickpkg I made into the / > > directory. > > Yes, I saw your posts on bug 125868 [1]. > > > ... and secondly, don't > > do it until you get some responses back from others who did it > succesfully. > > Well, I did it anyway (had a bit of time on my hands). And surprise, I > had the exact same symptoms as the bug above, i.e. a relocation error > before unmerging the previous glibc-2.3.6-r4. But everything was still > working ok. > > So I did *not* panic ;-) and just emerged glibc-2.4-r3 a second time (I > had made a binary package, so this was quite fast), and this time the > previous glibc was unmerged correctly. I suppose an emerge --prune would > also have worked. Your problem was most likely due to your having > unmerged glibc-2.4, which left you with a system without glibc. Is that what I said I did in the bug report? Ok, I did do something wrong. :-) Well for my MythTV box (the one I screwed up) I'll be waiting probably 6 months to a year to upgrade just to make sure there are no problems. Actually I'll probably just leave the new glibc and gcc hard-masked until I am forced to upgrade due to the old one being removed from portage or due to a dependancy. -- David Grant http://www.davidgrant.ca ------=_Part_227006_14702114.1158339145730 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 9/15/06, Remy Blank <remy.blank_asps@pobox.com> wrote:
David Grant wrote:
> I did and I totally screwed up my system. I managed to fix it eventually
> by booting to a live CD and untaring the quickpkg I made into the /
> directory.

Yes, I saw your posts on bug 125868 [1].

> ... and secondly, don't
> do it until you get some responses back from others who did it succesfully.

Well, I did it anyway (had a bit of time on my hands). And surprise, I
had the exact same symptoms as the bug above, i.e. a relocation error
before unmerging the previous glibc-2.3.6-r4. But everything was still
working ok.

So I did *not* panic ;-) and just emerged glibc-2.4-r3 a second time (I
had made a binary package, so this was quite fast), and this time the
previous glibc was unmerged correctly. I suppose an emerge --prune would
also have worked. Your problem was most likely due to your having
unmerged glibc-2.4, which left you with a system without glibc.

Is that what I said I did in the bug report? Ok, I did do something wrong. :-) Well for my MythTV box (the one I screwed up) I'll be waiting probably 6 months to a year to upgrade just to make sure there are no problems. Actually I'll probably just leave the new glibc and gcc hard-masked until I am forced to upgrade due to the old one being removed from portage or due to a dependancy.

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