2.4.18-0001-datatypes.patch removable in Changelog causes 2.4.20-r1 to failed to build. From Changelog: 21 Oct 2010; Tomáš Chvátal <scarabeus@gentoo.org> -files/2.4.18-0001-datatypes.patch, -libdrm-2.4.18_pre20100211-r1.ebuild, -libdrm-2.4.21.ebuild: old But in libdrm-2.4.20-r1.ebuild (lines 24--28) : PATCHES=( # Fixes buidling of x11-drivers/xf86-video-openchrome, Gentoo bug 298352, # upstream bug 26994 "${FILESDIR}"/2.4.18-0001-datatypes.patch ) Reproducible: Always Steps to Reproduce: 1. emerge libdrm-2.4.20 2. 3. Actual Results: >>> Unpacking source... >>> Unpacking libdrm-2.4.20.tar.bz2 to /var/tmp/portage/x11-libs/libdrm-2.4.20-r1/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/portage/x11-libs/libdrm/files/2.4.18-0001-datatypes.patch * ( 2.4.18-0001-datatypes.patch ) * ERROR: x11-libs/libdrm-2.4.20-r1 failed: * Cannot find $EPATCH_SOURCE! * * Call stack: * ebuild.sh, line 54: Called src_unpack * environment, line 3302: Called x-modular_src_unpack * environment, line 4193: Called x-modular_src_prepare * environment, line 4184: Called x-modular_patch_source * environment, line 4082: Called epatch '/usr/portage/x11-libs/libdrm/files/2.4.18-0001-datatypes.patch' * environment, line 1770: Called die * The specific snippet of code: * die "Cannot find \$EPATCH_SOURCE!"; * * If you need support, post the output of 'emerge --info =x11-libs/libdrm-2.4.20-r1', * the complete build log and the output of 'emerge -pqv =x11-libs/libdrm-2.4.20-r1'. * The complete build log is located at '/var/tmp/portage/x11-libs/libdrm-2.4.20-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-libs/libdrm-2.4.20-r1/temp/environment'. * S: '/var/tmp/portage/x11-libs/libdrm-2.4.20-r1/work/libdrm-2.4.20'
Thanks for the report. Fixed in CVS.
Thanks. Closing this bug.
x11-libs/libdrm-2.4.20-r1 failed to build without 2.4.18-0001-datatypes.patch