Calculating dependencies  
 * IMPORTANT: 4 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-apps/portage-2.2.0_alpha128
 * portage-2.2.0_alpha124.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...   [ ok ]
 * portage-2.2.0_alpha128.patch.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking portage-2.2.0_alpha124.tar.bz2 to /var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work
>>> Unpacking portage-2.2.0_alpha128.patch.bz2 to /var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work
>>> Source unpacked in /var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work
>>> Preparing source in /var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha124 ...
 * Applying portage-2.2.0_alpha128.patch ...

 * A dry-run of patch command succeeded, but actually
 * applying the patch failed!

 * Failed Patch: portage-2.2.0_alpha128.patch !
 *  ( /var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha128.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/sys-apps/portage-2.2.0_alpha128/temp/portage-2.2.0_alpha128.patch.out

 * ERROR: sys-apps/portage-2.2.0_alpha128 failed (prepare phase):
 *   Failed Patch: portage-2.2.0_alpha128.patch!
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_prepare
 *   environment, line 4766:  Called epatch '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha128.patch'
 *   environment, line 1548:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/portage-2.2.0_alpha128'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.2.0_alpha128'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha124'
 * S: '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha124'

>>> Failed to emerge sys-apps/portage-2.2.0_alpha128, Log file:

>>>  '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/temp/build.log'
 * Messages for package sys-apps/portage-2.2.0_alpha128:
 * A dry-run of patch command succeeded, but actually
 * applying the patch failed!
 * Failed Patch: portage-2.2.0_alpha128.patch !
 *  ( /var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha128.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/sys-apps/portage-2.2.0_alpha128/temp/portage-2.2.0_alpha128.patch.out
 * ERROR: sys-apps/portage-2.2.0_alpha128 failed (prepare phase):
 *   Failed Patch: portage-2.2.0_alpha128.patch!
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_prepare
 *   environment, line 4766:  Called epatch '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha128.patch'
 *   environment, line 1548:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/portage-2.2.0_alpha128'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.2.0_alpha128'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha124'
 * S: '/var/tmp/portage/sys-apps/portage-2.2.0_alpha128/work/portage-2.2.0_alpha124'