libconf-0.42.10-r2.ebuild contains the line epatch "${FILESDIR}/${PV}-per5.10.patch" which, obviously, should be epatch "${FILESDIR}/${PV}-perl5.10.patch" As a result: >>> Unpacking perl-Libconf-0.42.10.tar.bz2 to /var/tmp/portage/dev-util/libconf-0.42.10-r2/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/portage/dev-util/libconf/files/0.42.10-per5.10.patch * ( 0.42.10-per5.10.patch ) * ERROR: dev-util/libconf-0.42.10-r2 failed: * Cannot find $EPATCH_SOURCE! * * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2297: Called epatch '/usr/portage/dev-util/libconf/files/0.42.10-per5.10.patch' * environment, line 1077: Called die * The specific snippet of code: * die "Cannot find \$EPATCH_SOURCE!"; * * If you need support, post the output of 'emerge --info =dev-util/libconf-0.42.10-r2', * the complete build log and the output of 'emerge -pqv =dev-util/libconf-0.42.10-r2'. * The complete build log is located at '/var/log/portage/dev-util:libconf-0.42.10-r2:20091210-001024.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/libconf-0.42.10-r2/temp/environment'. * S: '/var/tmp/portage/dev-util/libconf-0.42.10-r2/work/perl-Libconf-0.42.10' >>> Failed to emerge dev-util/libconf-0.42.10-r2, Log file: >>> '/var/log/portage/dev-util:libconf-0.42.10-r2:20091210-001024.log' Reproducible: Always
SYNC before reporting issues like this.
(In reply to comment #1) > SYNC before reporting issues like this. Exactly. I synced, got bitten by this bug in the middle of a (moderately) long upgrade, and reported.
