I'm not sure if this is a portage bug or a problem with laptop-mode-tools, but when you have laptop-mode-tools 1.63-r2 installed with bluez-5.15 and you try to emerge net-libs/libbluedevil-2.0_rc1, you get a slot conflict because laptop-mode-tools tries to pull in bluez-4.101-r8 and libbluedevil won't allow it. Reproducible: Always Steps to Reproduce: 1. emerge laptop-mode-tools libbluedevil Actual Results: This is when trying to do a world update: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: net-wireless/bluez:0 (net-wireless/bluez-4.101-r8::gentoo, ebuild scheduled for merge) pulled in by net-wireless/bluez:0/0= required by (app-laptop/laptop-mode-tools-1.63-r2::gentoo, installed) (net-wireless/bluez-5.15::gentoo, installed) pulled in by >=net-wireless/bluez-5 required by (net-libs/libbluedevil-2.0_rc1::gentoo, ebuild scheduled for merge)
You are reading the Portage output wrong. $ grep bluez *.ebuild laptop-mode-tools-1.63-r2.ebuild: bluetooth? ( net-wireless/bluez:= ) laptop-mode-tools-1.63-r3.ebuild: bluetooth? ( net-wireless/bluez:= ) laptop-mode-tools-1.64.ebuild: bluetooth? ( net-wireless/bluez:= ) There is no '0/0=' dependency, but instead any version is allowed by laptop-mode-tools.
(In reply to Matthew Schultz from comment #0) > This is when trying to do a world update: Right, you possibly have to recompile packages you have installed using bluez. This bug is likely an case of "unclear" Portage output which caused misunderstanding of it.
Possible you want bug 500836
(In reply to Samuli Suominen from comment #3) > Possible you want bug 500836 Thanks for the help. I was able to fix it by unmerging laptop-mode-tools, upgrading libbluedevil and then reemerging laptop-mode-tools.
