* Package:    www-apache/mod_auth_kerb-5.4-r1
 * Repository: x-gentoo-x86
 * Maintainer: maintainer-needed@gentoo.org
 * USE:        amd64 elibc_glibc kernel_linux multilib userland_GNU
 * FEATURES:   preserve-libs sandbox
>>> Unpacking source...
>>> Unpacking mod_auth_kerb-5.4.tar.gz to /var/tmp/portage/www-apache/mod_auth_kerb-5.4-r1/work
 * Applying mod_auth_kerb-5.4-rcopshack.patch ...
 [ ok ]
 * Applying mod_auth_kerb-5.4-fixes.patch ...
 [ ok ]
 * Applying mod_auth_kerb-5.4-s4u2proxy.patch ...

 * Failed Patch: mod_auth_kerb-5.4-s4u2proxy.patch !
 *  ( /home/pinkbyte/dev/gentoo-dev/gentoo-x86/www-apache/mod_auth_kerb/files/mod_auth_kerb-5.4-s4u2proxy.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/www-apache/mod_auth_kerb-5.4-r1/temp/mod_auth_kerb-5.4-s4u2proxy.patch.out

 * ERROR: www-apache/mod_auth_kerb-5.4-r1 failed (unpack phase):
 *   Failed Patch: mod_auth_kerb-5.4-s4u2proxy.patch!
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_unpack
 *   environment, line 2253:  Called epatch '/home/pinkbyte/dev/gentoo-dev/gentoo-x86/www-apache/mod_auth_kerb/files/mod_auth_kerb-5.4-s4u2proxy.patch'
 *   environment, line 1090:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * 
 * If you need support, post the output of `emerge --info '=www-apache/mod_auth_kerb-5.4-r1'`,
 * the complete build log and the output of `emerge -pqv '=www-apache/mod_auth_kerb-5.4-r1'`.
 * This ebuild is from an overlay named 'x-gentoo-x86': '/home/pinkbyte/dev/gentoo-dev/gentoo-x86/'
 * The complete build log is located at '/var/tmp/portage/www-apache/mod_auth_kerb-5.4-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/www-apache/mod_auth_kerb-5.4-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/www-apache/mod_auth_kerb-5.4-r1/work/mod_auth_kerb-5.4'
 * S: '/var/tmp/portage/www-apache/mod_auth_kerb-5.4-r1/work/mod_auth_kerb-5.4'