nice one :) >>> kde-base/kdm-3.4.0_beta2 merged. kde-base/kdm selected: 3.4.0_beta1 protected: 3.4.0_beta2 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/kdm-3.4.0_beta1... No package files given... Grabbing a set. !!! ERROR: kde-base/kdm-3.4.0_beta1 failed. !!! Function get-parent-package, Line 385, Exitcode 0 !!! Package kde-base/kdebase-pam not found in KDE_DERIVATION_MAP, please report bug !!! If you need support, post the topmost build error, NOT this status message.
I removed kdebase-pam because it's not considered a split package anymore, and the ebuilds in portage (both kdm-3.4.0_beta1 and beta2) are aware of this. But it seems the one you have in /var/db it's not... what to do?
Nothing. Portage is smart enough to grab the files does it's cleaning job after presenting the error message. I just wanted to make everyone wild err... aware about it. ;) At best something like this shouldn't happen with stable packages, though.
We could have kept it in the derivation map with no ill effects. We can do that for stable packages if needed.
