The apache-patches-2.0.54-r7.tar.bz2 tarball untars to the directory apache-patches-2.0.54-r4. This of course causes problems as the ebuild is looking for -r7: >>> Unpacking httpd-2.0.54.tar.bz2 to /var/tmp/portage/apache-2.0.54-r7/work >>> Unpacking apache-patches-2.0.54-r7.tar.bz2 to /var/tmp/portage/apache-2.0.54-r7/work >>> Unpacking apache-conf-2.0.54-r7.tar.bz2 to /var/tmp/portage/apache-2.0.54-r7/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /var/tmp/portage/apache-2.0.54-r7/work/apache-patches-2.0.54-r7 * ( apache-patches-2.0.54-r7 )
Same with me also, it seems that the patch file on the server is incorrect and although is named apache-patches-2.0.54-r7.tar.bz2 it contains the -r4 directory inside. Any chance the patch on the server can be fixed... Cheers
Thanks for catching this, didn't even think about the path in the tarball when I renamed it to match the -r# of the -conf tarball. Fixed in CVS/Tarball uploaded.