When updating to kde 3.5.6, I've received some errors like this (includes the packages which have issues so far): >>> Auto-cleaning packages... kde-base/ksirc selected: 3.5.5-r1 protected: 3.5.6 omitted: none kde-base/kcontrol selected: 3.5.5 protected: 3.5.6 omitted: none kde-base/kicker selected: 3.5.5 protected: 3.5.6 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/ksirc-3.5.5-r1... !!! ERROR: /ksirc-3.5.5-r1 failed. Call stack: ebuild.sh, line 1508: Called source '/var/db/pkg/kde-base/ksirc-3.5.5-r1/ksirc-3.5.5-r1.ebuild' ksirc-3.5.5-r1.ebuild, line 8: Called inherit 'kde-meta' 'eutils' ebuild.sh, line 1253: 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 '/ksirc' kde-functions.eclass, line 369: 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/tmp/binpkgs/kde-base/ksirc-3.5.5-r1/temp/build.log'. !!! FAILED prerm: 1 A removal phase of the 'kde-base/ksirc-3.5.5-r1' package has failed with exit value 1. The problem occurred while executing the ebuild located at '/var/db/pkg/kde-base/ksirc-3.5.5-r1/ksirc-3.5.5-r1.ebuild'. If necessary, manually remove the ebuild in order to skip the execution of removal phases. Reproducible: Always
Do you have any kde*.eclass in overlay?
Only in an inactive overlay, and it's not an eclass in portage anyways...
Worked this out on IRC, it's a combination of using pkgcore (which doesn't write a CATEGORY file to the vdb) and a portage bug if the CATEGORY file doesn't exist.
Reassigning...
Created attachment 109811 [details, diff] reinsert CATEGORY into the environment if it's not predefined should do it, although a verification run might be wise.
This bug is related to 201082. It's fixed in svn r8832 to work with a missing CATEGORY file.