If I delete epiphany libsoup-gnome libproxy and try to reinstall epiphany it fails with: root@moose:/root(34)# emerge -C epiphany libsoup-gnome libproxy && emerge -v1D epiphany ... These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-libs/libproxy-0.4.2 USE="gnome networkmanager perl python webkit xulrunner -debug -kde -vala" 0 kB [ebuild N ] www-client/epiphany-2.30.2-r1 USE="doc networkmanager nss -avahi -debug -test" 0 kB [ebuild N ] net-libs/libsoup-gnome-2.30.2 USE="doc -debug (-introspection)" 0 kB ... >>> Installing (1 of 3) net-libs/libproxy-0.4.2 * checking 22 files for package collisions ... >>> Regenerating /etc/ld.so.cache... >>> Emerging (2 of 3) www-client/epiphany-2.30.2-r1 ... checking whether to build tests... no checking for DEPENDENCIES... configure: error: Package requirements ( glib-2.0 >= 2.19.7 gmodule-2.0 gthread-2.0 gio-unix-2.0 >= 2.19.7 gtk+-2.0 >= 2.19.5 gtk+-unix-print-2.0 >= 2.19.5 ice x11 sm libxml-2.0 >= 2.6.12 libxslt >= 1.1.7 gconf-2.0 libstartup-notification-1.0 >= 0.5 libnotify >= 0.4 webkit-1.0 >= 1.1.22 libsoup-gnome-2.4 >= 2.29.91 gnome-keyring-1 >= 2.26.0 ) were not met: No package 'libsoup-gnome-2.4' found Maybe there should a libsoup-gnome entry in DEPEND of epiphany-2.30.2-r1.ebuild? Reproducible: Always
Looks to me more like a portage problem: epiphany RDEPENDs on >=net-libs/libsoup-2.29.91[gnome] net-libs/libsoup PDEPENDs on libsoup-gnome But emerge chooses this order: # emerge -v1Da epiphany These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] www-client/epiphany-2.30.2-r1 USE="avahi nss test -debug -doc -networkmanager" 0 kB [ebuild N ] net-libs/libproxy-0.2.3-r3 USE="gnome python webkit xulrunner -kde -networkmanager" 0 kB [ebuild N ] net-libs/libsoup-gnome-2.30.2 USE="-debug -doc (-introspection)" 0 kB Even if libsoup-gnome can safely be installed in first time since libsoup is already installed
*** This bug has been marked as a duplicate of bug 199856 ***
Actually this is also a duplicate of bug #305423. See ChangeLog for details: 55 12 Apr 2010; Mart Raudsepp <leio@gentoo.org> epiphany-2.28.2.ebuild: 56 Fix libsoup dependencies - no need to dep on libsoup[gnome], configure 57 checks only libsoup-gnome and we dep on the split package already. Makes 58 things more user friendly for users with no global USE=gnome 84 11 Mar 2010; Gilles Dartiguelongue <eva@gentoo.org> 85 epiphany-2.24.3.ebuild, -epiphany-2.24.3-r10.ebuild, 86 -epiphany-2.26.3.ebuild, -epiphany-2.28.1.ebuild, epiphany-2.28.2.ebuild: 87 Clean up old revisions. Make sure libsoup-gnome is in RDEPEND, bug 88 #305423. The change was not inherited from 2.28 ebuild so I guess nobody checked changes done to the tree while the ebuild lived in overlay.
So the lost change of mine should get restored for 2.30 for the same benefit as I did it, and that would also workaround that portage bug...
Well, both mine and Gilles changes. libsoup-gnome dep instead of libsoup[gnome]. The idea was that after we split libsoup-gnome out of libsoup, that USE=gnome stays on libsoup only until all in-tree packages have converted from libsoup[gnome] to libsoup-gnome depends. So purely a migration path, so lets finish this migration for epiphany (again) at least.
+ 21 Jul 2010; Pacho Ramos <pacho@gentoo.org> epiphany-2.30.2-r1.ebuild: + RDEPEND directly on net-libs/libsoup-gnome per bug #327623 (by Juergen + Rose) following Mart Raudsepp and Gilles Dartiguelongue suggestions.
