I'm doing some major rebuilds of my KDE packages due to changed USE flags, and got this report from elog. The package kworldwatch was renamed to kworldclock in 3Q-2007, but the old ebuild was still around for the installed version of kdeartwork-kworldclock. As the ebuild calls deprange-dual unconditionally to set RDEPEND, the corresponding eclass should handle that call for the old name even if that package has been renamed in the meantime. That's what you get from packing so much KDE magic into the eclasses! ERROR: prerm ERROR: kde-base/kdeartwork-kworldclock-3.5.7 failed. Call stack: ebuild.sh, line 1541: Called source '/var/db/pkg/kde-base/kdeartwork-kworldclock-3.5.7/kdeartwork-kworldclock-3.5.7.ebuild' kdeartwork-kworldclock-3.5.7.ebuild, line 17: Called deprange-dual '3.5.7' '3.5.7' 'kde-base/kworldwatch' kde-functions.eclass, line 618: Called get-parent-package 'kde-base/kworldwatch' kde-functions.eclass, line 327: Called die Package kde-base/kworldwatch not found in KDE_DERIVATION_MAP, please report bug If you need support, post the topmost build error, and the call stack if relevant. A complete build log is located at '/var/log/portage/kde-base:kdeartwork-kworldclock-3.5.7:20070818-111941.log'. This ebuild is from an overlay: '/var/db/pkg/' The mentioned log file does not even exist, so there is not much more information that I can give you. I can only hope that there was nothing this ebuild should have removed but could not, because all package information seems to be overwritten by the newly merged version by now, and the emerge did continue even though this error looks fairly severe at first glance.
(In reply to comment #0) > That's what you get from packing so much KDE magic into the eclasses! Nope, that's what we get for pointless package moves such as Bug 188707 (previously Bug 122166). Next time similar requests will go to /dev/null and the bugs will be WONTFIXed. Definitely not worth all the hassle and trouble.
*** Bug 189429 has been marked as a duplicate of this bug. ***
I have re-added kworldwatch to the KDE_DERIVATION_MAP in kde-functions.eclass so that the dependency calculations can function properly again. (Sorry, I thought I had done that yesterday already but forgot to commit it.) Seeing the problems this caused, I agree with jakub - unless forced we should avoid package moves of this kind in the future and if we do it, we need to keep the old names in the KDE_DERIVATION_MAP. :)
*** Bug 189565 has been marked as a duplicate of this bug. ***
