gdal-1.6.1 tries to apply gdal-1.6.0-mysql_ogr_header.patch, but it seems it has already been applied upstream (?). * User-specified configure options are not set. * If needed, set GDAL_CONFIGURE_OPTS to enable grass support. * A dry-run of patch command succeeded, but actually * applying the patch failed! * Failed Patch: gdal-1.6.0-mysql_ogr_header.patch ! * ( /usr/portage/sci-libs/gdal/files/gdal-1.6.0-mysql_ogr_header.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sci-libs/gdal-1.6.1/temp/gdal-1.6.0-mysql_ogr_header.patch-4029.out * * ERROR: sci-libs/gdal-1.6.1 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3951: Called epatch '/usr/portage/sci-libs/gdal/files/gdal-1.4.2-datadir.patch' '/usr/portage/sci-libs/gdal/files/gdal-1.5.0-soname.patch' '/usr/portage/sci-libs/gdal/files/gdal-1.5.1-python-install.patch' '/usr/portage/sci-libs/gdal/files/gdal-1.6.0-swig-fix.patch' '/usr/portage/sci-libs/gdal/files/gdal-1.6.0-mysql_ogr_header.patch' '/usr/portage/sci-libs/gdal/files/gdal-1.6.1-ruby-make.patch' * environment, line 1865: Called epatch '/usr/portage/sci-libs/gdal/files/gdal-1.6.0-mysql_ogr_header.patch' * environment, line 2005: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: gdal-1.6.0-mysql_ogr_header.patch! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/sci-libs:gdal-1.6.1:20090803-215345.log'. * The ebuild environment file is located at '/var/tmp/portage/sci-libs/gdal-1.6.1/temp/environment'. *
The same problem here.
Created attachment 200125 [details] /var/tmp/portage/sci-libs/gdal-1.6.1/temp/gdal-1.6.0-mysql_ogr_header.patch-4224.out
Same here. Note that the dry-run of the patch succeeded, because dry-run uses -f which implies a forced forward application, with some fuzz in this case. The actual patch application otoh is done without -f, and therefore balks at the reversed patch. Probably a good thing, as we otherwise might have missed this duplication here, but it took me a while to figure out how this happens. I probably won't file a bug report against eutils.eclass for this, but if someone else wants to, feel free.
done
