I don't have sys-devel/patch installed, so this happens: * portage-2.1.11.9.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking portage-2.1.11.9.tar.bz2 to /var/tmp/portage/sys-apps/portage-2.1.11.9/work >>> Source unpacked in /var/tmp/portage/sys-apps/portage-2.1.11.9/work >>> Preparing source in /var/tmp/portage/sys-apps/portage-2.1.11.9/work/portage-2.1.11.9 ... * Setting portage.VERSION to 2.1.11.9 ... * Adding FEATURES=xattr to make.globals ... /var/tmp/portage/sys-apps/portage-2.1.11.9/temp/environment: line 4806: patch: command not found * ERROR: sys-apps/portage-2.1.11.9 failed (prepare phase): * Failed to patch make.conf.example * * Call stack: * ebuild.sh, line 85: Called src_prepare * environment, line 4806: Called die * The specific snippet of code: * patch make.conf "make.conf.${ARCH}".diff || die "Failed to patch make.conf.example";
Note that the problem seems to be only the missing ebuild dependency and certainly not with a problem during portage runtime. For that reason it seems wrong to me to set Component Core+Product Portage. This is merely a missing dependency in the portage ebuild, right?
Thanks, this is fixed in CVS.