Hi, I'm experiencing several issues installing kde-4.7 using sets, due to a change in package name. I've just downloaded newest kde set. Look here: [blocks B ] kde-base/kdebase-wallpapers:4 ("kde-base/kdebase-wallpapers:4" is blocking kde-base/kde-wallpapers-4.7.0) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (kde-base/kde-wallpapers-4.7.0::gentoo, installed) pulled in by >=kde-base/kde-wallpapers-4.7.0:4[-aqua] required by (kde-base/kdebase-startkde-4.7.0::gentoo, ebuild scheduled for merge) >=kde-base/kde-wallpapers-4.7.0:4[-aqua] required by (kde-base/kdebase-meta-4.7.0::gentoo, ebuild scheduled for merge) kde-base/kde-wallpapers required by @selected >=kde-base/kde-wallpapers-4.7.0:4[-aqua] required by (kde-base/kdebase-data-4.7.0::gentoo, ebuild scheduled for merge) (kde-base/kdebase-wallpapers-4.6.5::gentoo, ebuild scheduled for merge) pulled in by kde-base/kdebase-wallpapers:4 required by @kdebase-workspace ======== problem is that there's no kde-base/kdebase-wallpapers:4 in 4.7.0 but kde-base/kde-wallpapers-4.7.0 so I guess this explains the blocker. looking inside kde-workspace sets: kde-workspace -> kde-base/kdebase-wallpapers:4 kdebase-workspace-4.7 -> >=kde-base/kde-wallpapers-4.6.50 Reproducible: Always
*** Bug 376797 has been marked as a duplicate of this bug. ***
Ooook... given that you need to use a pmasked portage version just to be able to use sets, you should be able to figure that out on your own. :) I suggest you * remove the old, offending package with emerge -aC * change the sets * and then emerge the new sets (f.ex. with --noreplace)
yes, I've done that prior to report the bug, but I miss the point of your answer: I've reported it to have it fixed in portage and related files, not to fix my system, so to avoid others to fall in the same issue. Basically, I feel your answer to be a bit pointless: what's the point in having a bug reporting system if you tell to reporters "fix it in your system"? At least, you should provide an explanation why this is invalid or explain why this will no happen to other people. Honestly, not an answer that can be called useful to me, the bug is neither invalid or resolved.
