Am Dienstag, 8. September 2009 schrieb Massimiliano Ziccardi: > Already done.... > > localhost ~ # emerge --search bluez | egrep "bluez|installed" | egrep -v > "Homepage|Description" > [ Results for search key : bluez ] > * dev-python/pybluez > Latest version installed: [ Not Installed ] > * net-wireless/bluez > Latest version installed: [ Not Installed ] > * net-wireless/bluez-bluefw > Latest version installed: [ Not Installed ] > * net-wireless/bluez-firmware > Latest version installed: [ Not Installed ] > * net-wireless/bluez-gnome > Latest version installed: [ Not Installed ] > * net-wireless/bluez-hcidump > Latest version installed: [ Not Installed ] > * net-wireless/bluez-hciemu > Latest version installed: [ Not Installed ] > * net-wireless/bluez-libs > Latest version installed: [ Not Installed ] > * net-wireless/bluez-utils > Latest version installed: [ Not Installed ] > * sec-policy/selinux-bluez > Latest version installed: [ Not Installed ] > * x11-plugins/gkrellm-bluez [ Masked ] > Latest version installed: [ Not Installed ] > > > So I guess I don't have bluez anymore.... > > Any other idea?
You have some thing installed that needs bluez-3. So if you do --update world, both bluez versions are pulled in, and then they block each other. The solution is to remove the need for both of them, either by removing the package that needs bluez-3 or by removing its dependency on bluez by settings its use flags to bluetooth. $ equery d bluez -- Gruß | Greetings | Qapla' LOL, you said ROFL.
signature.asc
Description: This is a digitally signed message part.
