[ !! ] * ERROR: sys-devel/heirloom-devtools-070527-r2::gentoo failed (prepare phase): * patch -p1 failed with /usr/portage/sys-devel/heirloom-devtools/files/heirloom-devtools-070527-gcc6.patch * * Call stack: * ebuild.sh, line 115: Called src_prepare ----------------------------------------------------------------- This is an unstable amd64 chroot image (named 13.0-abi32+64_20170322-214044) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python3.5 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * java-config: The following VMs are available for generation-2:
Created attachment 469194 [details] emerge-info.txt
Created attachment 469196 [details] emerge-history.txt
Created attachment 469198 [details] environment
Created attachment 469200 [details] etc.portage.tbz2
Created attachment 469202 [details] sys-devel:heirloom-devtools-070527-r2:20170404-163345.log
Created attachment 469204 [details] temp.tbz2
Forgot to commit required patch file?
If the required patch file can't be added to the tree can we in the meantime get the line removed from the ebuild so this package builds again?
Created attachment 476212 [details, diff] Remove nonexistent patch application so the package works again. It doesn't seem very hard to fix this package, so it would be nice if it was fixed instead of remaining broken for months.
Please let me know what more I can do to get this package fixed.
[master 42e64e39bb3] sys-devel/heirloom-devtools: Really commit patch for fixing gcc6 support (#594090 and #614692) 2 files changed, 12 insertions(+), 1 deletion(-) create mode 100644 sys-devel/heirloom-devtools/files/heirloom-devtools-070527-gcc6.patch
