From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-amd64+bounces-12060-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1My7n6-000093-FR
for garchives@archives.gentoo.org; Wed, 14 Oct 2009 17:37:36 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 14B5BE0888;
Wed, 14 Oct 2009 17:37:35 +0000 (UTC)
Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.191])
by pigeon.gentoo.org (Postfix) with ESMTP id C8A6AE0888
for <gentoo-amd64@lists.gentoo.org>; Wed, 14 Oct 2009 17:37:34 +0000 (UTC)
Received: by gv-out-0910.google.com with SMTP id n29so327gve.39
for <gentoo-amd64@lists.gentoo.org>; Wed, 14 Oct 2009 10:37:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:content-type
:content-transfer-encoding;
bh=4BM5L3WMZDklHhYeVb6s28blFHoPE+B6USa6pnCq7MM=;
b=eL9S22q43JMRe9jh2cRLbd66SMyvt73FwKK0DhXEUtY3uZmbQwOmTjAFv9YlFPcWEL
N8/0Ah/3wpkrifq+4KVh1/F+4XBv173qJhkufsiDaoojH93FZ7yb2qPdpQSVHr9Qypxo
/GLWjUj/Xx5tYNKm3oUybejOErxKAYKSNZunY=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type:content-transfer-encoding;
b=xo+49NAmo+4QgU+j5SIA7C/xZLH5RN7SCFY3RQqgVlYMW0B+EVGd75o04KLY96E5u4
cicpAH+Q12asNITBFLUnOulCsnd5BdnnL6vRig6hri9n9OHC3cnqL95U+Os/+5trwgxS
QqYqIL0JUcEFFUcHmorWWlgvaQNeojKHOh/1Q=
Precedence: bulk
List-Post: <mailto:gentoo-amd64@lists.gentoo.org>
List-Help: <mailto:gentoo-amd64+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-amd64+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-amd64.gentoo.org>
X-BeenThere: gentoo-amd64@lists.gentoo.org
Reply-to: gentoo-amd64@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.103.80.20 with SMTP id h20mr3776129mul.21.1255541853681; Wed,
14 Oct 2009 10:37:33 -0700 (PDT)
In-Reply-To: <pan.2009.10.13.14.39.48@cox.net>
References: <20091013035841.GA20128@mars.lan>
<225000070910122331h374f8c6ar5eb883410b83c7be@mail.gmail.com>
<20091013132513.GA23274@mars.lan> <pan.2009.10.13.14.39.48@cox.net>
Date: Wed, 14 Oct 2009 14:37:33 -0300
Message-ID: <2a21586d0910141037x26acfd61ge16294c6591cdf2d@mail.gmail.com>
Subject: Re: [gentoo-amd64] Re: failing to emerge update
From: Mansour Al Akeel <mansour.alakeel@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 6461193f-7ee4-41c2-a7ad-82d078187662
X-Archives-Hash: 40d67f988f1e9f041425f687570e7973
I did revdep-rebuild and things went fine. When I did --depclean, It
removed many necessary packages. And I can not even complete
running "emerge system", it fails on one of the packages due to missing alo=
cal !
I can not even run mutt, as lynx is not there and can not install it as wel=
l.
I run this type of things before going to bed, as it takes time. I
should change this habit, and spend time on it when I am not tired. :)
I will look into this tonight, or maybe on the weekend. I may have to
spend many hours to fix this.
Normally I run "emerge --update --deep --newuse world" every two
weeks, but I haven't done this for more than 2 months. I don't this
should be an issue.
On Tue, Oct 13, 2009 at 11:39 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> Mansour Al Akeel posted on Tue, 13 Oct 2009 10:25:15 -0300 as excerpted:
>
>> I lost the output from the previos build, and unable to regenerate the
>> issue after fooliwnf libxcb update guilde. But now I am stuck with
>> another error, when bulllding gcc.
>>
>>
>> /var/tmp/portage/sys-devel/gcc-4.1.2/
>
> gcc-4.1.2 ? =A0gcc 4.1 is a bit outdated. =A0You /may/ be able to simply
> unmerge it. =A0What versions of gcc do you have installed, anyway? =A0It'=
s
> likely you have a 4.3 version, as gcc-4.3.2-r3 is the latest keyworded
> stable for amd64.
>
> A caution, however. =A0Until your whole system is rebuilt with the newer
> gccs, some C++ packages in particular may still link to the old
> versions. =A0But it should at least be possible to ignore the old gccs fo=
r
> the moment (emerge --resume --skipfirst if necessary) and build
> everything else. =A0If you're using FEATURES=3Dbuildpkg, it's easy enough=
to
> unmerge a package, see if anything breaks (run revdep-rebuild and see if
> there's anything that needs rebuilt, and hope it rebuilds fine), and
> remerge the binpkg if necessary. =A0That's what I'd do.
>
> If you're not running FEATURES=3Dbuildpkg, I'd suggest you consider it.
> Right before a system-wide rebuild is a great time to turn it on. =3D:^)
> But if you're not, you can use quickpkg to create a binpkg of a
> particular package before removing it for testing. =A0That way you still
> get the binpkg, and can remerge it if necessary, if you find you still
> need it.
>
> Anyway... after updating gcc to 4.3.2-r3 if you don't have it, and gcc-
> config-ing to it, you could emerge --emptytree @system @world so
> everything is built with it, and then unmerge older gcc versions,
> including the 4.1.2 that's giving you issues ATM.
>
> FWIW, on ~amd64, the only gcc I have currently installed is 4.4.1, as I
> unmerged earlier versions after I had rebuilt the entire system with it.
> I do remember having some issues rebuilding earlier gccs at one point,
> but with the entire system (other than those gccs) building with 4.4.1, I
> was able to unmerge them instead of rebuild them.
>
> Of course, I always do --update --deep --newuse, generally a couple times
> a week, and revdep-rebuild and --depclean afterward, to make sure the
> system stays consistent and keep the cruft to a minimum. =A0If you've let
> it build up by not regularly using --update --deep and not regularly
> doing --depcleans and revdep-rebuilds, you are likely to have quite some
> problems getting the system back in shape, as there will be quite some
> cruft buildup to clean out, and doing it incrementally as the updates
> show up is MUCH easier than letting it buildup and trying to do it all at
> once.
>
> --
> Duncan - List replies preferred. =A0 No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master." =A0Richard Stallman
>
>
>