Yesterday I happened to run emerge -pv @installed to check something, and I got a warning: emerge: there are no ebuilds to satisfy "kde-base/konq-plugins:4.2". I of course used the kde-4.2 sets as recommended in the kde4 guide, and they use slot 4.2. However, a quick equery list -pio konq-plugins resulted in this: * Searching for konq-plugins ... * installed packages: [I--] [ ~] kde-base/konq-plugins-3.5.10 (3.5) [I--] [M~] kde-base/konq-plugins-4.2.0 (4.2) * Portage tree (/p): [-P-] [ ] kde-base/konq-plugins-3.5.9 (3.5) [-P-] [ ~] kde-misc/konq-plugins-4.2.3 (4) * overlay tree (/p/layman/x11 /l/p): Oops! I've a three-micro-version outdated konq-plugins due to an incorrect 4.2.3 slot of 4 instead of 4.2! I don't know why it didn't trigger a protest earlier due to the removal of the ebuild and vacating of the slot in-tree (it's not in the overlays), but evidently sets and slots and dependencies interact such that it didn't. (Is that a portage bug too?) But yesterday I didn't want to bother syncing and updating, so I didn't file a bug until I checked again today after syncing. The problem remains. Lesson: emerge -p @installed isn't as useless as I thought it was for a system with a properly updated world file. One more bit of system hygiene to add to my routine post-update-deep-newuse revdep-rebuild and --depclean. The kde bug shouldn't need emerge --info, but if it's thought to be a portage bug, they might, so I'll attach. But I'm running portage-2.2_rc33.
Created attachment 193054 [details] emerge --info
remove kde-base/konq-plugins-4 and install kde-misc/konq-plugins:4. Everything is ok with the package. After talking with Samuli Suominen he adviced me to add an entry in profile/updates that we moved only the kde4 version of konq-plugins to kde-misc (as it was a mistake to put it in kde-base at first place, as it isn't shipped with official kde tarballs while the kde3 version is). I'll commit it now. Thanks
*** Bug 267644 has been marked as a duplicate of this bug. ***
