On Dienstag 08 September 2009, Alan McKinnon wrote:
> On Tuesday 08 September 2009 17:11:33 Massimiliano Ziccardi wrote:
> > Still no luck...
> >
> > Attached my new log...
> >
> > Any other idea?
> 
> From your log:
> 
> [nomerge      ] www-client/mozilla-firefox-3.0.13  USE="dbus gnome startup-
> notification xulrunner -bindist -custom-optimization -iceweasel -java -
> mozdevelop -restrict-javascript" LINGUAS="-af -ar -be -bg -bn -bn_IN -ca
>  -cs - cy -da -de -el -en -en_GB -en_US -eo -es -es_AR -es_ES -et -eu -fi
>  -fr -fy - fy_NL -ga -ga_IE -gl -gu -gu_IN -he -hi -hi_IN -hu -id -is -it
>  -ja -ka -kn -ko -ku -lt -lv -mk -mn -mr -nb -nb_NO -nl -nn -nn_NO -oc -pa
>  -pa_IN -pl -pt - pt_BR -pt_PT -ro -ru -si -sk -sl -sq -sr -sv -sv_SE -te
>  -th -tr -uk -zh -zh_CN -zh_TW"
> [nomerge      ]  gnome-base/libgnomeui-2.24.1  USE="-doc"
> [nomerge      ]   gnome-base/libgnome-2.24.1  USE="esd -debug -doc"
> [nomerge      ]    gnome-base/gvfs-1.0.3-r2  USE="bluetooth gnome hal
>  -archive -avahi -bash-completion -cdda -debug -doc -fuse -gnome-keyring
>  -gphoto2 - samba"
> [ebuild  N    ]     net-wireless/bluez-libs-3.36  USE="-debug" 0 kB
> 
> The basic problem is that bluez version 3 and 4 are incompatible. You can
>  have one or the other but not both. If packages want to give you both, you
>  have to persuade them to not give you the undesired one.
> 
> You need to learn to read the emerge output and see what is causing bluez-
> libs-3 to be emerged. In this case it is gvfs. That ebuild says this:
> 
> RDEPEND="
>       ...
>         bluetooth? (
>                 dev-libs/dbus-glib
> 
>                 >=net-wireless/bluez-libs-3.12
> 
> And bluez-libs is part of the version 3 package. The only way to solve this
>  is to stop gvfs from wanting bluez-libs. Several options:
> 
> You are installing kde-meta, do you really want all of gnome? Put -gnome in
> USE.
> 
> Do you really want gnome support in Firefox? Put -gnome in package.use for
> firefox
> 
> Do you use gvfs to access filesystems over bluetooth? Put -bluetooth in
> package.use for gvfs
> 
> Do you actually use bluetooth at all? Put -bluetooth in USE
> 

That covers pretty much all bases.

 If you don't wnat gnome - just put -gnome in make.conf (btw -alsa, are you 
sure about that? you have -alsa, -oss - you don't want sound?

set -gnome, if you don't want gnome. Then do an emerge -a --newuse world. Then 
emerge -a --depclean, and then retry. 

As long as gvfs with bluetooth flag is around, you will have that blockers. As 
long as several packages of you have the gnome flag, they will pull in gvfs.

Reply via email to