epatch can't find the file to patch because src_unpack incorrectly cd's somewhere first (patch attached). Reproducible: Always Steps to Reproduce: 1. emerge =sys-libs/db-3.2.9-r10 Actual Results: fails Expected Results: succeed
Created attachment 54675 [details, diff] Proposed fix The problem is that src_unpack does this: cd ${WORKDIR}/${P}/dist ... epatch ${FILESDIR}/${P}-jarlocation.patch epatch ${FILESDIR}/db-3.2.9-java15.patch -jarlocation.patch works because it only touches files in dist, so it succeeds on -p2 or something. -java15.patch fails. This patch puts the missing cd back in so the current directory is sensible.
This ebuild was also commited to stable on all arches, which is against procedures as it is not a security related issue. Please revert the keywords to ~arch and triple check before commiting to make sure everything works in the future. Thanks :)
*** Bug 87027 has been marked as a duplicate of this bug. ***
Paul, please fix your patch. This is *exactly* the reason why ebuilds are not auto-stablized on any arch in non-security situations. Please in the future do not mark arches stable in ebuilds that you can't test and/or are not part of that respective arch's team.
Ok, I fucked up the cd thing. I should probably have tested things better first. This version however is far from brand-new. It has been untouched for months. And in testing for that amount of time too.
But as been discussed many times on the gentoo-dev ML, you do not have carte blanche to mark an ebuild stable across the board, regardless of how long it as been in testing. Please follow procedure as its there for a reason.
sparc stable now.
I guess this is fixed now
