public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerge world looking grim
Date: Mon, 24 Aug 2015 09:59:21 -0400	[thread overview]
Message-ID: <CAGfcS_mU73t1-WyoqVqBZOr40ByNX2mkgujTR8=TD+xdqNZO3Q@mail.gmail.com> (raw)
In-Reply-To: <20150824133959.GB622@apio.adsroot.itcs.umich.edu>

On Mon, Aug 24, 2015 at 9:39 AM, Alec Ten Harmsel
<alec@alectenharmsel.com> wrote:
> On Mon, Aug 24, 2015 at 09:35:36AM -0400, Harry Putnam wrote:
>> Alan Mackenzie <acm@muc.de> writes:
>>
>> > I'd recommend you then just to reinstall.  Remembering my fights with
>> > stupid error messages from emerge, and so on, I wish I'd just
>> > reinstalled months earlier than I did.
>>
>> Thanks for the frank suggestions and noted lack unix hero
>> talk... hehe.
>
> I personally think that updating glibc and gcc, then continuing with the
> rest of the system update is the easiest path forward. You won't lose
> your portage config, it will probably be a little bit faster, and it
> requires a lot less manual intervention (running a handful of commands
> vs. following the handbook)..
>

Agree. I probably get update issues of this complexity at least
annually.  I couldn't tell you when I installed my stage3 on this box,
but it was a LONG time ago and I'm constantly cleaning up /etc cruft
from things being moved around.

I would not rush to just reinstall a gentoo box unless you get really
stuck, or this is part of a configuration management workflow (which I
fully encourage - there is something to be said for blowing away your
install and reinstalling every time you do a package update, just to
demonstrate that you're able to do it from a disaster-recovery
standpoint).

-- 
Rich


  reply	other threads:[~2015-08-24 13:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24  2:19 [gentoo-user] emerge world looking grim Harry Putnam
2015-08-24  4:48 ` Jc García
2015-08-24 10:28 ` Alec Ten Harmsel
2015-08-24 12:41 ` Rich Freeman
2015-08-24 13:35   ` Alec Ten Harmsel
2015-08-24 13:17 ` Alan Mackenzie
2015-08-24 13:35   ` [gentoo-user] " Harry Putnam
2015-08-24 13:39     ` Alec Ten Harmsel
2015-08-24 13:59       ` Rich Freeman [this message]
2015-08-24 14:05         ` wraeth
2015-08-24 13:44     ` Alan McKinnon
2015-08-24 13:42   ` [gentoo-user] " Alan McKinnon
2015-08-24 14:46     ` [gentoo-user] " Harry Putnam
2015-08-24 15:28       ` Alan McKinnon
2015-08-24 16:49         ` Jeremi Piotrowski
2015-08-24 19:18           ` Alan McKinnon
2015-08-25  0:56         ` Dale
2015-08-25 22:00         ` Harry Putnam
2015-08-24 18:26       ` Rich Freeman
2015-08-25 22:02         ` Harry Putnam
2015-08-25 22:10         ` Harry Putnam
2015-08-25 23:09           ` Jeremi Piotrowski
2015-08-27  7:46             ` Harry Putnam
2015-08-24 13:46 ` James
2015-08-24 14:52   ` Rich Freeman
2015-08-24 15:36     ` James
2015-08-24 18:19       ` Rich Freeman
2015-08-25 15:05         ` James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGfcS_mU73t1-WyoqVqBZOr40ByNX2mkgujTR8=TD+xdqNZO3Q@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox