Reporting for user. He tried to emerge -C libksirtet resulting.. -- cut -- kde-base/libksirtet selected: 3.5.5 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging kde-base/libksirtet-3.5.5... !!! ERROR: kde-base/libksirtet-3.5.5 failed. Call stack: ebuild.sh, line 1511: Called source '/var/db/pkg/kde-base/libksirtet-3.5.5/libksirtet-3.5.5.ebuild' libksirtet-3.5.5.ebuild, line 7: Called inherit 'kde-meta' ebuild.sh, line 1256: Called qa_source '/usr/portage/eclass/kde-meta.eclass' ebuild.sh, line 28: Called source '/usr/portage/eclass/kde-meta.eclass' kde-meta.eclass, line 116: Called get-parent-package 'kde-base/libksirtet' kde-functions.eclass, line 323: Called die !!! Package 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:libksirtet-3.5.5:20070317-005759.log'. !!! FAILED prerm: 1 A removal phase of the 'kde-base/libksirtet-3.5.5' package has failed with exit value 1. The problem occurred while executing the ebuild located at '/var/db/pkg/kde-base/libksirtet-3.5.5/libksirtet-3.5.5.ebuild'. If necessary, manually remove the ebuild in order to skip the execution of removal phases. -- cut -- #gentoo-bugs 08:45 <+drac> Try editing /usr/portage/eclass/kde-functions.eclass 08:46 <+drac> Add something like "kde-base/kdegames kde-base/libksirtet" to KDE_DERIVATION_MAP next to the others. 09:15 < analyzer> deleted:) 09:16 <+drac> so it worked? 09:16 < analyzer> this package deleted 09:16 < analyzer> :-) So that worked for him, if it's an right solution or not that I do not know.
Dupe of 170286
http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/libksirtet/?hideattic=0 Not in portage, but WAS in portage. That's why you don't go around editing eclasses once they've been committed.
*** Bug 170286 has been marked as a duplicate of this bug. ***
http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/kde-functions.eclass?r1=1.143&r2=1.144
The question here is why someone who isn't part of the KDE team did this unimportant and seemingly trivial fix, but managed to screw it and neither one cleaned up afterwards - well Zac readded two other incorretly removed entries soon after. Piotr, did you actually ask someone from the KDE team, if it's fine touching the eclass, before breaking KDE tree wide? We basically can't incompatibly change stuff once introduced in eclasses, so even removing entries for dead packages isn't a good idea. The most entries stem from the days the split kde ebuilds were experimental, which shouldn't matter anymore. I readded a couple older ones, though. Considering fixed.
