>>> Verifying ebuild manifests

>>> Emerging (1 of 1) net-im/viber-9999-r9999::d7-Overlay
 * viber.deb SHA256 SHA512 WHIRLPOOL size ;-) ...                          [ ok ]
>>> Unpacking source...
>>> Unpacking viber.deb to /var/tmp/portage/net-im/viber-9999-r9999/work
>>> Source unpacked in /var/tmp/portage/net-im/viber-9999-r9999/work
>>> Preparing source in /var/tmp/portage/net-im/viber-9999-r9999/work ...
>>> Unpacking ./control.tar.gz to /var/tmp/portage/net-im/viber-9999-r9999/work
>>> Unpacking ./data.tar.xz to /var/tmp/portage/net-im/viber-9999-r9999/work
 * Applying viber-9999-desktop.patch ...

 * Failed Patch: viber-9999-desktop.patch !
 *  ( /home/user/Overlay/net-im/viber/files/viber-9999-desktop.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/net-im/viber-9999-r9999/temp/viber-9999-desktop.patch.out

 * ERROR: net-im/viber-9999-r9999::d7-Overlay failed (prepare phase):
 *   Failed Patch: viber-9999-desktop.patch!
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 1952:  Called epatch '/home/user/Overlay/net-im/viber/files/viber-9999-desktop.patch'
 *   environment, line  716:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 *
 * If you need support, post the output of `emerge --info '=net-im/viber-9999-r9999::d7-Overlay'`,
 * the complete build log and the output of `emerge -pqv '=net-im/viber-9999-r9999::d7-Overlay'`.
 * The complete build log is located at '/var/tmp/portage/net-im/viber-9999-r9999/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-im/viber-9999-r9999/temp/environment'.
 * Working directory: '/var/tmp/portage/net-im/viber-9999-r9999/work'
 * S: '/var/tmp/portage/net-im/viber-9999-r9999/work'