public inbox for gentoo-desktop@lists.gentoo.org
 help / color / mirror / Atom feed
From: marduk@letterboxes.org
To: gentoo-desktop@lists.gentoo.org
Subject: Re: [gentoo-desktop] Problem Emerging Gnome3 on Fresh Install
Date: Thu, 17 Oct 2013 12:44:21 -0400	[thread overview]
Message-ID: <1382028261.12495.35226749.21F38387@webmail.messagingengine.com> (raw)
In-Reply-To: <20131017144457.GA2600@ghostwheel>



On Thu, Oct 17, 2013, at 10:44 AM, Tyrin Price wrote:
> Greetings,
> 
> I am a newbie to Gentoo but not new to Linux and I am having
> difficulty setting up Gnome3 on a fresh Gentoo install.
> 
> I've read many wiki entries and tips online. So far the best advice I
> received was on IRC but I am still stopped.
> 
> Here is what I have done:
> 
> Fresh install (amd64 architecture).
> 
> Added ACCEPT_KEYWORDS="~amd64" to /etc/portage/make.conf
> 
> Emerged dbus and added it to services started at boot time.
> 
> Changed profile to gnome/systemd
> 
> Now, I cannot figure out how to get around the problems shown when I
> try to emerge gnome.
> 
> http://pastebin.com/NsbycC27 shows the output of emerge gnome

[blocks B      ] sys-fs/udev ("sys-fs/udev" is blocking
sys-apps/systemd-208-r2)
[blocks B      ] <sys-apps/openrc-0.12 ("<sys-apps/openrc-0.12" is
blocking sys-apps/kmod-15)
[blocks B      ] sys-apps/systemd ("sys-apps/systemd" is blocking
sys-fs/udev-204)

Blocks 1 and 3 are the same: You can't have systemd and sys-fs/udev
installed simultaneously.  Block 2 is telling you you need to upgrade or
uninstall openrc before you pull in kmod-15.

However, I strongly suggest you *not* do a huge upgrade this way.  If
it's a new install and you are initally on "amd64" My recommendation is
to follow these steps:

1. Say on amd64.  Bring yourself to a consistent state (emerge -DuvaN
@world; revdep-rebuild; emerge --depclean --ask)
2. Switch to ~amd64.  Bring yourself to a consistent state. 
3. Switch to systemd (Read the wiki article). Bring yourself to a
consistent state.
4. emerge gnome.

Doing everything at once (IMO) is just a recipe for headaches.  The best
thing is to do smaller steps, verify, then move to the next step.  Sure
you can do everything in one step, but when there is a problem it will
be more difficult to figure out which change created which problem (was
it switching to testing? switching to systemd? etc.).

HTH,
-a


  reply	other threads:[~2013-10-17 16:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 14:44 [gentoo-desktop] Problem Emerging Gnome3 on Fresh Install Tyrin Price
2013-10-17 16:44 ` marduk [this message]
2013-10-17 19:50   ` [gentoo-desktop] " Duncan
2013-10-18  1:48   ` [gentoo-desktop] " Tyrin Price
2013-10-19  2:27   ` Tyrin Price
2013-10-19  2:39     ` Tyrin Price
2013-10-19 13:39     ` marduk
2013-10-19 14:13       ` Tyrin Price
2013-10-19 14:43         ` marduk
2013-10-19 23:17   ` Tyrin Price

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=1382028261.12495.35226749.21F38387@webmail.messagingengine.com \
    --to=marduk@letterboxes.org \
    --cc=gentoo-desktop@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