Summary: | net-libs/libproxy-0.4.7 is linking against gnome-base/gconf | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fab <netbox253> |
Component: | [OLD] Unspecified | Assignee: | Freedesktop bugs <freedesktop-bugs> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
libproxy-0.4.7 build log
new build.log with upstream's patch applied |
Description
Fab
2012-01-26 13:51:06 UTC
Oddly enough that dependency is present in the 0.4.6-r3 ebuild but not in 0.4.7. That file is not installed on my system, please provide full build.log for libproxy Created attachment 300049 [details] libproxy-0.4.7 build log I got the build log by running the following command : > ebuild /portage/trees/gentoo/net-libs/libproxy/libproxy-0.4.7.ebuild compile Maybe this is due some problem when disabling "gnome" support :-/ Created attachment 300339 [details] new build.log with upstream's patch applied I'm not sure at 100%, but I think the problem should be fixed by applying the following patch coming from upstream's trunk : http://code.google.com/p/libproxy/source/detail?r=823 I tried to apply it manually and I rebuilt libproxy with it (using the same ebuild command as above), the new build log is attached. Can someone please confirm with real emerge ? on my system libproxy is built like this : > > $ emerge -pv libproxy > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild R ] net-libs/libproxy-0.4.7 USE="-gnome -kde -mono > -networkmanager -perl -python -test" 0 kB Thanks. Sorry for late reply but is this still a problem ? It looks like all ebuilds in tree are currently only enabling Gnome 3 support which discards gconf completely so it should not be a problem anymore. (In reply to Gilles Dartiguelongue from comment #6) > Sorry for late reply but is this still a problem ? > It looks like all ebuilds in tree are currently only enabling Gnome 3 > support which discards gconf completely so it should not be a problem > anymore. But gconf is still a dependency for some non-gnome3 packages in the tree : > $ equery d gconf > * These packages depend on gconf: > app-office/libreoffice-bin-4.2.6.3-r2 (gnome ? gnome-base/gconf:2) > dev-python/gconf-python-2.28.1-r1 (>=gnome-base/gconf-2.11.1) > games-util/steam-client-meta-0-r20141204 (gnome-base/gconf:2[abi_x86_32]) > media-plugins/gst-plugins-gconf-0.10.31-r1 (>=gnome-base/gconf-2.32.4-[[long-string]]) > media-video/ogmrip-1.0.1 (gtk ? gnome-base/gconf) > net-voip/ekiga-4.0.0-r1 (gconf ? >=gnome-base/gconf-2.6.0:2) > x11-libs/wxGTK-2.8.12.1-r1 (gstreamer ? gnome-base/gconf:2) Anyway, it is not longer a problem *for me*, net-libs/libproxy uninstalled on my systems. Well sure but the question here is "is libproxy still linking to gconf ?" right ? I do have gconf installed and libproxy does not link to it. I do not have this /usr/libexec/pxgconf executable installed as well. |