I have searched over all the posts about this topic and still cant solve it... Iḿ getting gnome-3.8 in my machinne and i have the famous conflict of libsoup-gnome with libsoup. Here i will post all the codes so maybe you can help me...

Code:

Artemisa # emerge -C net-libs/libsoup-gnome
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean <atom>` to check for reverse dependencies before
* removing packages.

--- Couldn't find 'net-libs/libsoup-gnome' to unmerge.

>>> No packages selected for removal by unmerge

(oc i unmerged it some minutes ago but this one is for you to check it)

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

net-libs/libsoup:2.4

(net-libs/libsoup-2.42.2::gentoo, installed) pulled in by
>=net-libs/libsoup-2.42.1:2.4 required by (www-client/epiphany-3.8.2::gentoo, ebuild scheduled for merge)
(and 10 more with the same problem)

(net-libs/libsoup-2.40.3::gentoo, ebuild scheduled for merge) pulled in by
~net-libs/libsoup-2.40.3[introspection?] required by (net-libs/libsoup-gnome-2.40.3::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. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

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

Iĺd post my unmasking file but i dont think its necesary unless you say so. Greetings and i hope somebody can help me, this is the first time i post on the forums asking for help and i've been using gentoo since i have memory (and i'm 27, well, since it saw the light and was the first system able to pull me out of slackware)

Last edited by Skirmitch on Mon Jun 17, 2013 8:58 pm; edited 1 time in total

That emerge output isn't really readable.
Check with '-t'.
Try putting libsoup-gnome into mask - maybe that way you'll see what's pulling it (besides old libsoup, that is).
Chances are you're simply missing a package or two in keyword file.

That emerge output isn't really readable.
Check with '-t'.
Try putting libsoup-gnome into mask - maybe that way you'll see what's pulling it (besides old libsoup, that is).
Chances are you're simply missing a package or two in keyword file.

Does this tell you anything? I dont use totem so i dont care if it doesnt get installed but not sure what the others do and dont know exactly how to prevent them from being merged either without generating dependence conflicts.

Code:

emerge =gnome-base/gnome-3.8.0 -t >> emerge_forum

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

net-libs/libsoup:2.4

(net-libs/libsoup-2.42.2::gentoo, installed) pulled in by
>=net-libs/libsoup-2.42.1:2.4 required by (www-client/epiphany-3.8.2::gentoo, ebuild scheduled for merge)
(and 10 more with the same problem)

(net-libs/libsoup-2.40.3::gentoo, ebuild scheduled for merge) pulled in by
~net-libs/libsoup-2.40.3[introspection?] required by (net-libs/libsoup-gnome-2.40.3::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. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

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

The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by dev-libs/totem-pl-parser-2.32.6-r3
# required by media-video/totem-3.8.2
# required by gnome-base/gnome-core-apps-3.8.0
# required by gnome-base/gnome-3.8.0
# required by =gnome-base/gnome-3.8.0 (argument)
# /etc/portage/package.mask:
=net-libs/libsoup-gnome-2.40.3

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.

Well, for a start put something >=totem-pl-parser-3.4.4 into keywords and recheck.

Ok, tbh i really dont know what i just did but i just did it blindly. Here is the result after adding it to accept_keywords:

Code:

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

net-libs/libsoup:2.4

(net-libs/libsoup-2.42.2::gentoo, installed) pulled in by
>=net-libs/libsoup-2.42.1:2.4 required by (www-client/epiphany-3.8.2::gentoo, ebuild scheduled for merge)
(and 10 more with the same problem)

(net-libs/libsoup-2.40.3::gentoo, ebuild scheduled for merge) pulled in by
~net-libs/libsoup-2.40.3[introspection?] required by (net-libs/libsoup-gnome-2.40.3::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. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

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

The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by dev-libs/totem-pl-parser-2.32.6-r3
# required by media-video/totem-3.8.2
# required by gnome-base/gnome-core-apps-3.8.0
# required by gnome-base/gnome-3.8.0
# required by =gnome-base/gnome-3.8.0 (argument)
# /etc/portage/package.mask:
=net-libs/libsoup-gnome-2.40.3

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

net-libs/libsoup:2.4

(net-libs/libsoup-2.42.2::gentoo, installed) pulled in by
>=net-libs/libsoup-2.42.1:2.4 required by (www-client/epiphany-3.8.2::gentoo, ebuild scheduled for merge)
(and 11 more with the same problem)

(net-libs/libsoup-2.40.3::gentoo, ebuild scheduled for merge) pulled in by
~net-libs/libsoup-2.40.3[introspection?] required by (net-libs/libsoup-gnome-2.40.3::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. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

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

The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by dev-libs/libgweather-3.6.2
# required by gnome-extra/evolution-data-server-3.8.3[weather]
# required by gnome-extra/gnome-contacts-3.8.2
# required by net-im/empathy-3.8.3[gnome]
# required by gnome-base/gnome-core-apps-3.8.0
# required by gnome-base/gnome-3.8.0
# required by =gnome-base/gnome-3.8.0 (argument)
# /etc/portage/package.mask:
=net-libs/libsoup-gnome-2.40.3

For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

Btw, i would like to know whats the logic behind what we are doing. We are accepting higher versions of some packages but they should still need libsoup-gnome to function, i dont understand why they stop needing it when we upgrade them

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

dev-libs/vala-common:0

(dev-libs/vala-common-0.18.1::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)

(dev-libs/vala-common-0.20.1::gentoo, ebuild scheduled for merge) pulled in by
>=dev-libs/vala-common-0.20.1 required by (dev-lang/vala-0.20.1::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. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

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

The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
# required by dev-lang/vala-0.20.1
# required by gnome-extra/evolution-data-server-3.8.3[vala]
# required by gnome-extra/gnome-contacts-3.8.2
# required by net-im/empathy-3.8.3[gnome]
# required by gnome-base/gnome-core-apps-3.8.0
# required by gnome-base/gnome-3.8.0
# required by =gnome-base/gnome-3.8.0 (argument)
=dev-libs/vala-common-0.20.1 ~x86

(dev-lang/vala-0.14.2-r2::gentoo, ebuild scheduled for merge) pulled in by
dev-lang/vala:0.14[vapigen] required by (net-libs/gssdp-0.12.2.1::gentoo, ebuild scheduled for merge)

For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

I SUPPOSE that the Vala problem can be solved by pulling gssdp to 0.14.13 which has ~x86 keyword but the introspection one i dont know how to fix it (iḿ not sure about the Vala one neither, i dont know how dangerous is to accept ~x86 masks all the time)

Ok, fixed the problem with emerge -u world by adding =gnome-base/gnome-3.8.0 to keywords. Now i'm only stuck with this which happends either if i emerge -u world or if i emerge =gnome-base/gnome-3.8.0: