previously we have two ebuild net-libs/libsoup and net-libs/libsoup-gnome for version 2.40.3, but now one ebuild for version 2.42.x? and those packages depend on ebuild libsoup-gnome should be fixed if libsoup version 2.42 been pulled in. those are ebuilds which installed in my system # equery -C d libsoup-gnome * These packages depend on libsoup-gnome: dev-libs/libgdata-0.13.3 (gnome ? >=net-libs/libsoup-gnome-2.37.91:2.4[introspection?]) dev-libs/libgweather-3.6.2 (>=net-libs/libsoup-gnome-2.25.1:2.4) gnome-base/gvfs-1.15.4 (>=net-libs/libsoup-gnome-2.34.0) net-libs/gnome-online-accounts-3.6.3 (>=net-libs/libsoup-gnome-2.38:2.4) net-libs/libsocialweb-0.25.21 (gnome ? >=net-libs/libsoup-gnome-2.25.1:2.4) net-libs/rest-0.7.90 (gnome ? >=net-libs/libsoup-gnome-2.25.1:2.4) sys-libs/libosinfo-0.2.4 (net-libs/libsoup-gnome:2.4) Reproducible: Always !!! 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, ebuild scheduled for merge) pulled in by >=net-libs/libsoup-2.42.0:2.4[introspection?] required by (dev-libs/libgdata-0.13.4::gentoo, ebuild s cheduled for merge) (and 2 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, installe d)
sorry, seems this already solved, all I have to do is "emerge -C libsoup-gnome"
I guess we can add a note about how to resolve this blocker (or even, tell people to run "emerge -avuDN world --unmerge libsoup-gnome", but I haven't tried it)
Anyway, running "--deselect" should be enough as portage is able to resolve the blocker automatically in that case (libsoup-gnome not being in world file)
Added a comment to the guide: https://wiki.gentoo.org/wiki/GNOME/3.8-upgrade-guide#Obsolete_software
