Created attachment 271751 [details] emerge --info =x11-libs/vte-0.28.0-r300 My ebuild of vte-0.28.0-r300 fails with: >>> Emerging (2 of 2) x11-libs/vte-0.28.0-r300 * vte-0.28.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * Package: x11-libs/vte-0.28.0-r300 * Repository: gentoo * Maintainer: gnome@gentoo.org * USE: doc elibc_glibc introspection kernel_linux userland_GNU x86 * FEATURES: sandbox >>> Unpacking source... >>> Unpacking vte-0.28.0.tar.bz2 to /var/tmp/portage/x11-libs/vte-0.28.0-r300/work >>> Source unpacked in /var/tmp/portage/x11-libs/vte-0.28.0-r300/work >>> Preparing source in /var/tmp/portage/x11-libs/vte-0.28.0-r300/work/vte-0.28.0 ... * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/portage/x11-libs/vte/files/vte-0.28.0-fix-gdk-targets.patch * ( vte-0.28.0-fix-gdk-targets.patch ) * ERROR: x11-libs/vte-0.28.0-r300 failed (prepare phase): * Cannot find $EPATCH_SOURCE! * * Call stack: * ebuild.sh, line 56: Called src_prepare * environment, line 3288: Called epatch '/usr/portage/x11-libs/vte/files/vte-0.28.0-fix-gdk-targets.patch' * environment, line 1634: Called die * The specific snippet of code: * die "Cannot find \$EPATCH_SOURCE!"; * * If you need support, post the output of 'emerge --info =x11-libs/vte-0.28.0-r300', * the complete build log and the output of 'emerge -pqv =x11-libs/vte-0.28.0-r300'. * The complete build log is located at '/var/tmp/portage/x11-libs/vte-0.28.0-r300/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-libs/vte-0.28.0-r300/temp/environment'. * S: '/var/tmp/portage/x11-libs/vte-0.28.0-r300/work/vte-0.28.0' >>> Failed to emerge x11-libs/vte-0.28.0-r300, Log file: >>> '/var/tmp/portage/x11-libs/vte-0.28.0-r300/temp/build.log' While this may be a mirror delay I wanted to document it in case it isn't known already.
Created attachment 271753 [details] emerge -pqv =x11-libs/vte-0.28.0-r300
Created attachment 271755 [details] Build Log
Created attachment 271757 [details] Environment
Fixed in the tree, thanks for reporting!
*** Bug 365421 has been marked as a duplicate of this bug. ***
*** Bug 365569 has been marked as a duplicate of this bug. ***