following ebuild line epatch "${FILESDIR}"/${PN/-pvgrub/}-4.2.0-jserver.patch doesn't match filename provided as below /usr/portage/app-emulation/xen-pvgrub/files/xen-pvgrub-4.2-jserver.patch Reproducible: Sometimes localizing package in /usr/local/portage patching the ebuild by replacing faulty line with epatch "${FILESDIR}"/${PN}-4.2-jserver.patch and digesting the ebuild "ebuild ebuild-full-path-and-name" digest did the trick here. As stated above, it didn't happen all the time because it is compiled and installed here! So it should be a regression ...
Hi to all the Xen gentOOists
ebuild xen-pvgrub-4.2.2-r1.ebuild clean prepare Appending /newaches/gentoo/cvs/gentoo-x86 to PORTDIR_OVERLAY... * xen-4.2.2.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * grub-0.97.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * zlib-1.2.3.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * pciutils-2.2.9.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * lwip-1.3.0.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * newlib-1.16.0.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * XSA-55patches.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking xen-4.2.2.tar.gz to /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work >>> Unpacking grub-0.97.tar.gz to /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work >>> Unpacking zlib-1.2.3.tar.gz to /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work >>> Unpacking pciutils-2.2.9.tar.bz2 to /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work >>> Unpacking lwip-1.3.0.tar.gz to /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work >>> Unpacking newlib-1.16.0.tar.gz to /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work >>> Unpacking XSA-55patches.tar.gz to /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work >>> Source unpacked in /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work >>> Preparing source in /home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work/xen-4.2.2 ... * Applying xen-4.2.1-externals.patch ... [ ok ] * Applying xen-4-fix_dotconfig-gcc.patch ... [ ok ] * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /newaches/gentoo/cvs/gentoo-x86/app-emulation/xen-pvgrub/files/xen-4.2.0-jserver.patch * ( xen-4.2.0-jserver.patch ) * ERROR: app-emulation/xen-pvgrub-4.2.2-r1::gentoo failed (prepare phase): * Cannot find $EPATCH_SOURCE! * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 5252: Called epatch '/newaches/gentoo/cvs/gentoo-x86/app-emulation/xen-pvgrub/files/xen-4.2.0-jserver.patch' * environment, line 1587: Called die * The specific snippet of code: * die "Cannot find \$EPATCH_SOURCE!"; * * If you need support, post the output of `emerge --info '=app-emulation/xen-pvgrub-4.2.2-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/xen-pvgrub-4.2.2-r1::gentoo'`. * The complete build log is located at '/keeps/gentoo/emergelogs/wim/app-emulation:xen-pvgrub-4.2.2-r1:20130918-144225.log'. * For convenience, a symlink to the build log is located at '/home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/temp/build.log'. * The ebuild environment file is located at '/home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/temp/environment'. * Working directory: '/home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work/xen-4.2.2' * S: '/home/jer/portage/app-emulation/xen-pvgrub-4.2.2-r1/work/xen-4.2.2'
~/cvsPortage/gentoo-x86/app-emulation/xen-pvgrub $ ebuild xen-pvgrub-4.2.2-r1.ebuild clean prepare =========================================== * zlib Makefile edited * tarballs moved to source >>> Source prepared. seems I missed re-naming it in xen-pvgrub-4.2.2-r1, thanks for picking it up. 26 Sep 2013; Ian Delaney <idella4@gentoo.org> xen-pvgrub-4.2.2-r1.ebuild: Correct jserver.patch name in xen-pvgrub-4.2.2-r1, fixes Bug #485248