From: Alec Ten Harmsel <alec@alectenharmsel.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge world looking grim
Date: Mon, 24 Aug 2015 06:28:06 -0400 [thread overview]
Message-ID: <20150824102752.GA27243@greenbeast> (raw)
In-Reply-To: <87lhd1ig1t.fsf@reader.local.lan>
On Sun, Aug 23, 2015 at 10:19:42PM -0400, Harry Putnam wrote:
> My gentoo OS is running on Openindiana (solaris) inside oracle's vbox.
>
> It's been left setting for at least 4-5 months maybe a couple more.
>
> After eix-sync, attempting an `emerge vuND world' comes up with so
> many blocks, use flag changes and a variety of other bad news in
> such proliferation... I'm thinking better to install from scratch with
> latest ISO.
>
> ,----
> | NOTE: The full mess can be viewed here:
> |
> | zeus.jtan.com/~reader/vutxt/images/emerge_MassiveFailure-150823.txt
> `----
No, this really shouldn't be that bad. Look at the list of updates and
apply certain updates first. glibc and gcc should probably be updated
first, so just run:
emerge -uDN1 glibc
Since gcc-config could not find gcc 4.7, it is marked as stable, and
emerge was not trying to install it, you must have a version hard-coded
in `/var/lib/portage/world`. For now, to upgrade gcc you can just grab
the newest version:
emerge --oneshot gcc
From then on, it should go relatively smoothly, since emerge was
handling all of the blockers.
> Can anyone advise me which iso to use? And which profile to set for
> general use in a vbox, hopefully to allow a `no sweat' emerge to a
> full OS.
As Jc Garcia mentioned, Gentoo is not a `no sweat' distro.
Alec
next prev parent reply other threads:[~2015-08-24 10:28 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 [this message]
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
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=20150824102752.GA27243@greenbeast \
--to=alec@alectenharmsel.com \
--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