After moving plasna-nm from kde-misc/ to kde-plasma/ category at 2016/10/29 kde-apps/solid-runtime[networkmanager] depends on kde-misc/plasma-nm, while it should depend on :4 slot of it. Otherwise there is a number of conflicts during update: Reproducible: Always Steps to Reproduce: # emerge -avuDN world ... [ebuild N ~] kde-plasma/plasma-workspace-5.8.2:5::gentoo USE="calendar -debug -geolocation -gps -handbook (-prison) -qalculate -semantic-desktop {-test}" 6 792 KiB [ebuild NS ~] kde-plasma/plasma-nm-5.8.2:5::gentoo [0.9.3.6:4::gentoo] USE="-debug -modemmanager -openconnect -teamd" 629 KiB [uninstall ] kde-plasma/plasma-nm-0.9.3.6:4::gentoo USE="(-aqua) -debug -modemmanager -openconnect" L10N="ru -ar -bg -bs -ca -ca-valencia -cs -da -de -el -en-GB -eo -es -et -fa -fi -fr -ga -gl -hr -hu -is -it -ja -km -ko -lt -lv -mai -mr -ms -nb -nds -nl -nn -pa -pl -pt -pt-BR -ro -sk -sl -sr -sr-Latn -sr-Latn-ijekavsk -sr-ijekavsk -sv -th -tr -ug -uk -zh-CN -zh-TW" [blocks b ] kde-plasma/plasma-nm:4 ("kde-plasma/plasma-nm:4" is blocking kde-plasma/plasma-nm-5.8.2) [blocks B ] kde-base/libtaskmanager:4 ("kde-base/libtaskmanager:4" is blocking kde-plasma/plasma-workspace-5.8.2) [blocks B ] kde-base/systemsettings:4 ("kde-base/systemsettings:4" is blocking kde-plasma/kwin-5.8.2) [blocks B ] kde-base/ksysguard:4 ("kde-base/ksysguard:4" is blocking kde-plasma/ksysguard-5.8.2, kde-plasma/libksysguard-5.8.2) [blocks B ] kde-base/ksplash:4 ("kde-base/ksplash:4" is blocking kde-plasma/plasma-workspace-5.8.2) [blocks B ] kde-base/krunner:4 ("kde-base/krunner:4" is blocking kde-plasma/plasma-workspace-5.8.2) [blocks B ] kde-base/plasma-workspace:4 ("kde-base/plasma-workspace:4" is blocking kde-plasma/plasma-workspace-5.8.2) [blocks B ] kde-base/ksmserver:4 ("kde-base/ksmserver:4" is blocking kde-plasma/plasma-workspace-5.8.2) [blocks B ] kde-base/kdebase-startkde:4 ("kde-base/kdebase-startkde:4" is blocking kde-plasma/plasma-workspace-5.8.2) [blocks B ] kde-base/kwin:4 ("kde-base/kwin:4" is blocking kde-plasma/kwin-5.8.2) [blocks B ] kde-base/klipper:4 ("kde-base/klipper:4" is blocking kde-plasma/plasma-workspace-5.8.2) [blocks B ] kde-base/kcminit:4 ("kde-base/kcminit:4" is blocking kde-plasma/plasma-workspace-5.8.2)
Maybe the same thing should be done with kde-plasma/bluedevil while it also was moved from kde-misc/ category to kde-plasma/ simultaneously with plasna-nm
The commits: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9b65b90b2942ce7673855a6b9ba738892d47e9a0 https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ce272f34d6dafedb450bcaf8a7e888b4dd9cd8e5 kde-plasma/plasma-nm:* means "any slot of kde-plasma/plasma-nm is acceptable" and by default portage will choose the highest version. If you do not want to use Plasma 5 you could work around by masking plasma-nm:4 but beware we are planning to remove Plasma 4 quite soon.
Yes, I'd masked :5 slot of bluedevil and plasma-nm before reported this bug and all was OK. It's just strange that solid-runtime, which is :4 only depends on :* slot of other packages.
solid-runtime doesn't actually depend on either, they're "convenience" USE flags that were added in bug #471362.
Yes, I understand. So there are 2 possible solutions/workarounds: - mask :5 slot of these packages - disable "bluetooth" and "networkmanager" flags for solid-runtime and just install :4 slots of packages independently. So, I think bug can be closed as having workarounds, especially in connection with the coming removal of plasma 4.
Thanks. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d53e596c423123becd42fabd00bb16cf0662da28
