From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Gnome 3.2.2 Block
Date: Fri, 02 Dec 2011 15:21:42 -0800 [thread overview]
Message-ID: <jbbmd3$erh$1@dough.gmane.org> (raw)
In-Reply-To: <CAGSnHaCZc_0Vpq+V3vF_wdba5Atiy9bD9U6TQMqY6YrcrbxUcQ@mail.gmail.com>
On 12/01/2011 06:13 PM, Jason Weisberger wrote:
> From a fresh install, upgrading from Gnome 2.26, I'm trying to install gnome 3.2.2, but getting nowhere fast.
> I stopped using Gentoo back before slots became common, so maybe I'm missing something as far as that goes.
>
> jbdubbspc jbdubbs # emerge -pv =gnome-base/gnome-3.2.1
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [blocks b ] <gnome-base/gdm-2.91.94 ("<gnome-base/gdm-2.91.94" is blocking gnome-base/gnome-control-center-3.2.2)
> [blocks B ] <media-libs/clutter-1.7 ("<media-libs/clutter-1.7" is blocking media-libs/cogl-1.8.2)
> [blocks B ] <dev-python/pygobject-2.28.6-r50:2[introspection] ("<dev-python/pygobject-2.28.6-r50:2[introspection]" is blocking dev-python/pygobject-3.0.2)
Notice that gdm is blocked with a 'b' and the other two with a 'B'. That
means that portage is smart enough to fix the gdm conflict, but you must
fix the other two yourself. I've found that the quickest fix for the 'B'
blockers is just to remove them with emerge -C. So far I've not had any
problems with that approach.
next prev parent reply other threads:[~2011-12-02 23:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 2:13 [gentoo-user] Gnome 3.2.2 Block Jason Weisberger
2011-12-02 2:14 ` [gentoo-user] " Jason Weisberger
2011-12-02 23:21 ` walt [this message]
2011-12-02 23:27 ` [gentoo-user] " Jason Weisberger
2011-12-03 0:10 ` Neil Bothwick
2011-12-03 2:09 ` Jason Weisberger
2011-12-03 3:15 ` Jason Weisberger
2011-12-03 3:37 ` Jason Weisberger
2011-12-03 15:51 ` [gentoo-user] " walt
2011-12-03 17:10 ` Jason Weisberger
2011-12-04 17:15 ` Jason Weisberger
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='jbbmd3$erh$1@dough.gmane.org' \
--to=w41ter@gmail.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