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.43) id 1E9vuG-00028Z-19 for garchives@archives.gentoo.org; Tue, 30 Aug 2005 02:31:24 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7U2STvD029403; Tue, 30 Aug 2005 02:28:29 GMT Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.197]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7U2OsVZ007332 for ; Tue, 30 Aug 2005 02:24:54 GMT Received: by xproxy.gmail.com with SMTP id h31so691629wxd for ; Mon, 29 Aug 2005 19:26:55 -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=f1YMFdZI5FFK2ZiesY0akTojNuRq8ERJZtM/4JtJa0WFsDIC0Iy5tveoIvrEp1Z/uo9DmIyu/EjNMJPxCb9rx+2WgVvRvvTe8j6C1zp/EkhsAuBQagcL95M9zp27RtrqGMbaSEP0ayIHw48IvAENZwWDFboIPpIM/X3WcSw8dK0= Received: by 10.70.94.4 with SMTP id r4mr117358wxb; Mon, 29 Aug 2005 19:26:55 -0700 (PDT) Received: by 10.70.116.18 with HTTP; Mon, 29 Aug 2005 19:26:55 -0700 (PDT) Message-ID: <642958cc05082919266a14411d@mail.gmail.com> Date: Mon, 29 Aug 2005 22:26:55 -0400 From: Mark Shields To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] To emerge -e world or not to emerge -e world? In-Reply-To: <431352CE.8040603@erols.com> 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_1117_2225085.1125368815302" References: <431352CE.8040603@erols.com> X-Archives-Salt: 1f0bc325-824c-4c14-add7-887a44b7e134 X-Archives-Hash: 249cb14c3669cb19f174bad0edd47b2a ------=_Part_1117_2225085.1125368815302 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Depending on what you have installed, it will take more than 14 hours. Are= =20 you sure they're talking about emerge -e system and not emerge -e world? On 8/29/05, Matt Randolph wrote: >=20 > I know that upgrading glibc can cause some programs to break if they > were built against the previous glibc. This happens to me all the time > and I have gotten in the habit of simply re-emerging any packages that > misbehave since a glibc upgrade. >=20 > Well, I have upgraded both glibc and gcc within the last week or so. > And I've been contemplating a kernel upgrade too. I looked at genlop > and it said it will take a mere fourteen hours to re-emerge everything > with an emerge -e world. I'm tempted to do it, but I'm wary of making > major changes to a system that currently seems to be working perfectly. >=20 > However, I've only tested a handful of packages (the ones that I use > every day) since the glibc upgrade, and I did have to rebuild a few of > them. For this reason, I'm guessing that a significant number of the > packages that I haven't tested are actually broken too. So when I say > my system seems to be working perfectly, I think that only applies to > the packages that I interact with daily and probably not to some of the > ones that I don't. >=20 > When does it make sense to re-emerge everything? I've heard some people > say never but that others do it perhaps monthly or even more often. >=20 > Is there a (significant) risk that something will go wrong? Even > terribly wrong? >=20 > Is it possible that some important programs aren't working right now due > to having been built against an older glibc, and that I'm simply > oblivious to the fact that they aren't working? I'm worried > specifically about system programs that I don't usually have reason to > interact with, yet may be vitally important to the security and > stability of my system. > -- > gentoo-user@gentoo.org mailing list >=20 >=20 --=20 - Mark Shields ------=_Part_1117_2225085.1125368815302 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Depending on what you have installed, it will take more than 14 hours.  Are you sure they're talking about emerge -e system and not emerge -e world?

= On 8/29/05, Matt = Randolph <mattr@erols.com>= wrote:
I know tha= t upgrading glibc can cause some programs to break if they
were built ag= ainst the previous glibc.  This happens to me all the time
and I have gotten in the habit of simply re-emerging any packages that<= br>misbehave since a glibc upgrade.

Well, I have upgraded both glibc= and gcc within the last week or so.
And I've been contemplating a kerne= l upgrade too.  I looked at genlop
and it said it will take a mere fourteen hours to re-emerge everything<= br>with an emerge -e world.  I'm tempted to do it, but I'm wary o= f making
major changes to a system that currently seems to be working pe= rfectly.

However, I've only tested a handful of packages (the ones that I us= e
every day) since the glibc upgrade, and I did have to rebuild a few of=
them.  For this reason, I'm guessing that a significant numbe= r of the
packages that I haven't tested are actually broken too.  So w= hen I say
my system seems to be working perfectly, I think that only app= lies to
the packages that I interact with daily and probably not to some= of the
ones that I don't.

When does it make sense to re-emerge everythi= ng?  I've heard some people
say never but that others do it pe= rhaps monthly or even more often.

Is there a (significant) risk that= something will go wrong?  Even
terribly wrong?

Is it possible that some important programs aren= 't working right now due
to having been built against an older glibc, an= d that I'm simply
oblivious to the fact that they aren't working? &= nbsp;I'm worried
specifically about system programs that I don't usually have reason to<= br>interact with, yet may be vitally important to the security and
stabi= lity of my system.
--
gento= o-user@gentoo.org mailing list




-- - Mark Shields ------=_Part_1117_2225085.1125368815302-- -- gentoo-user@gentoo.org mailing list