I'm trying to update my system but ran into several issues, most of which appear to be related to the new version of gnome. I really dont want to deal with systemd. Is there an easy way to block this (I dont use the gnome desktop)? I tried simply adding ">=gnome-base/gnome-3.6.2" to package.mask but it didn't help.

(dev-libs/icu-51.2::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

net-libs/webkit-gtk:3

(net-libs/webkit-gtk-2.0.4::gentoo, ebuild scheduled for merge) pulled in by
>=net-libs/webkit-gtk-1.11.92:3[jit?] required by (www-client/epiphany-3.8.2::gentoo, ebuild scheduled for merge)

(net-libs/webkit-gtk-1.10.2-r300::gentoo, installed) pulled in by
>=net-libs/webkit-gtk-1.6:3/3= required by (net-libs/libproxy-0.4.11-r1::gentoo, installed)

dev-libs/boost:0

(dev-libs/boost-1.52.0-r6::gentoo, ebuild scheduled for merge) pulled in by
dev-libs/boost:0/1.52= required by (kde-base/kleopatra-4.10.5::gentoo, installed)
>=dev-libs/boost-1.43:0/1.52= required by (kde-base/rocs-4.10.5::gentoo, installed)
dev-libs/boost:0/1.52= required by (kde-base/kdepim-runtime-4.10.5-r1::gentoo, installed)
(and 1 more with the same problems)

(dev-libs/boost-1.53.0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

sys-auth/pambase:0

(sys-auth/pambase-20120417-r2::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(sys-auth/pambase-20120417-r2::gentoo, ebuild scheduled for merge) pulled in by
sys-auth/pambase[systemd] required by (gnome-base/gdm-3.8.3.1::gentoo, ebuild scheduled for merge)

dev-util/boost-build:0

(dev-util/boost-build-1.52.0-r1::gentoo, installed) pulled in by
=dev-util/boost-build-1.52.0-r1 required by (dev-libs/boost-1.52.0-r6::gentoo, ebuild scheduled for merge)

(dev-util/boost-build-1.53.0::gentoo, ebuild scheduled for merge) pulled in by
=dev-util/boost-build-1.53* required by (dev-libs/boost-1.53.0::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.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.

* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.

The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
# required by gnome-base/gdm-3.8.3.1
# required by gnome-base/gnome-3.8.0
# required by @selected
# required by @world (argument)
>=sys-auth/pambase-20120417-r2 systemd

!!! The following installed packages are masked:
- sci-geosciences/googleearth-7.1.1.1871::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Julian Ospald <hasufell@gentoo.org> (21 Jul 2013)
# Mask all unfetchable versions and those with tons of random
# bugs and segfaults (all). Don't ask for a version bump unless
# there is a working release.

The problem is you threw too small a net. You only caught the meta package. Try masking gnome-base/* and unmask any packages (including versions) as needed._________________First things first, but not necessarily in that order.

The problem is you threw too small a net. You only caught the meta package. Try masking gnome-base/* and unmask any packages (including versions) as needed.

Thanks. I use some gnome apps and dont want to completely remove it from my system. I just dont want to update to the new versions which seem to require systemd. It looks like I have 3.6.2 installed currently. Is there a (relatively easy) way to do mask all new gnome-related packages (at least until the systemd issues are resolved)?

Not using wild cards. They have to be version-less due to parsing issues. There are 3 options

mask every package including version you don't want

mask all gnome packages and then unmask what you want using version specifiers

switch to using stable gnome applications.

You can generate a list of packages you want to add using eix -sIC --only-names gnome which will include all packages with "gnome" in their name. You will need eix installed for it tor work. That should make it easer to enter into which ever file you prefer. Personally, I would go with the mask approach. That way any new dependencies will have to be approved and you won't have to deal with unexpected visits from systemd or bugs from mixing versions. If you are clever with sed and awk you could probably rig them to provide the appropriate symbol and version in a nice one liner.

EDIT: corrected eix command_________________First things first, but not necessarily in that order.

I have run into this and have made the decision to just remove gnome.
Cinnamon unfortunetly is classed as a gnome app so for now I shall have to remove them all_________________the table is made from wood. forget what you learnt, the table is made from carbon. forget what you learnt, the table is made from protons. forget what you learnt, the table is made from quarks. forget what you learnt, the table is good for shagging on

The rot seems to set in at version 3.8 of anything. That's not sufficient. I'm also using --backtrack=50 so that portage can resolve things.
This list will only grow - find another desktop you can live with._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

The rot seems to set in at version 3.8 of anything. That's not sufficient. I'm also using --backtrack=50 so that portage can resolve things.
This list will only grow - find another desktop you can live with.

(dev-libs/icu-51.2::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

net-libs/libsoup:2.4

(net-libs/libsoup-2.42.2::gentoo, ebuild scheduled for merge) pulled in by
>=net-libs/libsoup-2.42 required by (dev-libs/libgdata-0.13.3::gentoo, installed)
(and 9 more with the same problem)

(net-libs/libsoup-2.40.3::gentoo, installed) pulled in by
~net-libs/libsoup-2.40.3[introspection?] required by (net-libs/libsoup-gnome-2.40.3::gentoo, installed)

dev-libs/boost:0

(dev-libs/boost-1.52.0-r6::gentoo, ebuild scheduled for merge) pulled in by
dev-libs/boost:0/1.52= required by (kde-base/kleopatra-4.10.5::gentoo, installed)
>=dev-libs/boost-1.43:0/1.52= required by (kde-base/rocs-4.10.5::gentoo, installed)
dev-libs/boost:0/1.52= required by (kde-base/kdepim-runtime-4.10.5-r1::gentoo, installed)
(and 1 more with the same problems)

(dev-libs/boost-1.53.0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

media-libs/cogl:1.0

(media-libs/cogl-1.14.0::gentoo, ebuild scheduled for merge) pulled in by
>=media-libs/cogl-1.14.0:1.0=[introspection?,pango] required by (media-libs/clutter-1.14.4::gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)

(media-libs/cogl-1.12.2-r1::gentoo, installed) pulled in by
media-libs/cogl:1.0/11= required by (net-im/empathy-3.6.4::gentoo, installed)

dev-util/boost-build:0

(dev-util/boost-build-1.52.0-r1::gentoo, installed) pulled in by
=dev-util/boost-build-1.52.0-r1 required by (dev-libs/boost-1.52.0-r6::gentoo, ebuild scheduled for merge)

(dev-util/boost-build-1.53.0::gentoo, ebuild scheduled for merge) pulled in by
=dev-util/boost-build-1.53* required by (dev-libs/boost-1.53.0::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.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.

* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.

Any suggestions on how to proceed? I'm not sure how/where to put the -~amd64 mentioned in another response.

Why does gentoo even have a systemd use flag if its not really optional anymore? I'm tempted to do a fresh install w/o gnome (but keeping the gtk libs) but it looks like thunderbird requires it. I think that and ghex2 are the gnome apps I use so I might have to find replacements if I end up going that route.

But on my most used desktop (~amd64) I realized that even libreoffice.bin depends heavily on gnome ebuilds.
I didn't follow them to the end, but it seems to me, that for desktops with lots of Software installed, there will be probably no way around sytemd.
Also dependencies may change over time and we may get into more troubles when swimming against the upstream.

_________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I finally managed to update my system (all but octave and a few other similar programs that have compile issues) with gnome frozen at 3.6.2. In case it helps anyone I've included package.mask below. Note that this is a temporary solution 'til I have time to re-install with -gnome and -systemd (and -pulseaudio).

At the risk of stating the obvious, it should be possible to switch to a new desktop with very little disruption to your work. First, simply set the use flags and emerge your replacement (xfce, i3, kde, etc). Once that is complete you can enter your new environment and use something like emerge -ac $(eix -sIC --only-names gnome) at your convenience. At your next update, simply include the ND options. Once your update finishes, run emerge -ac as there should be several orphaned dependencies._________________First things first, but not necessarily in that order.

'til I have time to re-install with -gnome and -systemd (and -pulseaudio).

It is no need to reinstall. To do it, I done an emerge world. It gave me a lot of blockers. I removed them with "emerge -C blocking_packges" until emerge world was happy._________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

At the risk of stating the obvious, it should be possible to switch to a new desktop with very little disruption to your work. First, simply set the use flags and emerge your replacement (xfce, i3, kde, etc). Once that is complete you can enter your new environment and use something like emerge -ac $(eix -sIC --only-names gnome) at your convenience. At your next update, simply include the ND options. Once your update finishes, run emerge -ac as there should be several orphaned dependencies.

Thanks. I use fluxbox exclusively but I do occasionally run a few kde and gnome apps which is why I have it installed. If I can completely remove gnome and pulseaudio from my existing system, I'd prefer to do that rather than reinstall. I'll try your suggestions and those from Dominique_71 and see how it goes...

Personally, it dislike more *kit than systemd. But anyway, when I see all the threads with issues about the systemd migration into udev, I am happy to use eudev. You may be interested by that thread too._________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

ugh...this was horrible. I'm still trying to keep gnome-3 off my machine, using gnome-2.32.
I thought Gentoo was going to maintain 2.32 for a long while? Should be an easy way to keep gnome3 off, but this has been proving to be difficult...

Shouldn't there be a separate profile for gnome3 and gnome2?_________________Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSDWhat am I supposed to be advocating?

Why doesn't the gnome-2 meta-ebuild (as well as perhaps any other metapackage like xorg) specify maximum versions, so that the gnome3 packages don't get depended... I suppose the same can go for gnome 3.6 but that's a bit more complicated..._________________Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSDWhat am I supposed to be advocating?