(virtual/udev-171::gentoo, ebuild scheduled for merge) pulled in by
=virtual/udev-171 required by (sys-fs/eudev-0::gentoo, ebuild scheduled for merge)
<virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, ebuild scheduled for merge)
(and 1 more with the same problems)

(virtual/udev-196::gentoo, installed) pulled in by
=virtual/udev-196 required by (dev-libs/libatasmart-0.19::gentoo, ebuild scheduled for merge)
>=virtual/udev-196[gudev,hwdb] required by (sys-fs/udisks-2.0.90::gentoo, ebuild scheduled for merge)
(and 19 more with the same problems)

(virtual/udev-171::gentoo, ebuild scheduled for merge) pulled in by
=virtual/udev-171 required by (net-wireless/bluez-4.99::gentoo, ebuild scheduled for merge)
<virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, ebuild scheduled for merge)
(and 18 more with the same problems)

(virtual/udev-196::gentoo, installed) pulled in by
>=virtual/udev-196[gudev,hwdb] required by (sys-fs/udisks-2.0.90::gentoo, ebuild scheduled for merge)

It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

virtual/udev:0

(virtual/udev-171::gentoo, ebuild scheduled for merge) pulled in by
=virtual/udev-171 required by (sys-fs/eudev-0::gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)

(virtual/udev-196::gentoo, installed) pulled in by
=virtual/udev-196 required by (dev-libs/libatasmart-0.19::gentoo, ebuild scheduled for merge)
>=virtual/udev-196[gudev,hwdb] required by (sys-fs/udisks-2.0.90::gentoo, ebuild scheduled for merge)
(and 19 more with the same problems)

(virtual/udev-171::gentoo, ebuild scheduled for merge) pulled in by
=virtual/udev-171 required by (sys-fs/eudev-0::gentoo, ebuild scheduled for merge)
<virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, ebuild scheduled for merge)
(and 1 more with the same problems)

This tells us that you probably have some mix-up with arch/~arch keywords, and some of them are not sufficient for >=udev-196.

What should have been done is putting the next lvm2 version supporting >=udev-192 into package.keywords, then emerge -1v lvm2, then look for the next package ('and 1 more with the same problems'). Also, if you wanted to switch to eudev, you could either do that by emerging eudev-0 coming from udev-171, or eudev-1 (which needs to be unmasked too) coming from udev-196 (which seems to be installed)._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

Thanks for the reply all I want to do is install gnome light 3.6.2 how do you guys unmask that do you use autounmask-write or what because thats all I do and I can install any other window manager or desktop with no problem but for some reason I have this problem every time I want to install a version of gnome 3.this is going on my fourth day of fighting this.

I am really sorry I do not at all mean to sound rude I am just VERY frustrated. I have been at this for four days now I wasted my whole weekend now. Another question I install with my profile set to 1 and after I get a working base gentoo system I change my profile to four and use autounmask-write to unmask gnome. Could this be part of my problem? Is this a bad idea? How do you guys do this? Thanks.

I am really sorry I do not at all mean to sound rude I am just VERY frustrated. I have been at this for four days now I wasted my whole weekend now. Another question I install with my profile set to 1 and after I get a working base gentoo system I change my profile to four and use autounmask-write to unmask gnome. Could this be part of my problem? Is this a bad idea? How do you guys do this? Thanks.

Did you add the keyword changes to package.accept_keywords _________________Good luck

Glad it's working now: I really don't advise running an unstable system across the board, personally. You can end up in trouble with just about any system component, and you'll just be told that's what you get for running unstable (along with help to fix it, but it's usually a similar amount of hassle to what you've been through when things do fall apart.) What it really comes down to is this:

aortell24 wrote:

how do you guys unmask that do you use autounmask-write or what because thats all I do

..and I use update (an emerge wrapper) for that, since it does it all within the same interface: it'll write the changes after confirmation, and show the diff of the unmask/keywords files. I say "same interface" as I can also review the list in a dialog and see what USE flags are about, and perhaps change them. It does a whole load of other stuff (mostly to do with keeping the system in shape); it helps to make day-to-day admin pretty simple.

Then again, I'm biased as I'm one of the original authors, and its current maintainer ;)

This same problem has been keeping me from doing an update for a while now.

It took some time, but the keys were (to the best of my recount)
1) unmasking (package.accept_keywords) the latest versions of a bunch of packages, including lvm2 virtual/shadow bluez sys-apps/shadow
2) masking (package.mask) =virtual/udev-171, but NOT masking =sys-fs/udev-171

In fact, since OP's predicament (and frustration) sounds so similar to mine, I'll go ahead and post all my portage files. I'm on an Acer 771G running amd64 with Gnome 3. I'm slow to jump to new kernel versions b/c I'm still manually patching in code to fix the sh***y touchpad Acer decided to use for this model.

make.conf

Code:

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CFLAGS="-O2 -march=core2 -pipe"
PORTAGE_TMPDIR = "/work/portage/temp"
DISTDIR = "/work/portage/dist"
MAKEOPTS="-j16"
CXXFLAGS="${CFLAGS}"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="x86_64-pc-linux-gnu"
VIDEO_CARDS="intel nouveau"
INPUT_DEVICES="evdev keyboard mouse synaptics"
# These arde the USE flags that were used in addition to what is provided by the
# profile used for building.