+++ This bug was initially created as a clone of Bug #179567 +++ Hi, Trying to emerge =fluxbox-0.9.15.1-r2 produces the following error >>> Unpacking source... >>> Unpacking fluxbox-0.9.15.1.tar.bz2 to /var/tmp/portage/x11-wm/fluxbox-0.9.15 .1-r2/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/portage/x11-wm/fluxbox/files/0.9.15/fluxbox-0.9.15-our-styles-go-over- here.patch * ( fluxbox-0.9.15-our-styles-go-over-here.patch ) * * ERROR: x11-wm/fluxbox-0.9.15.1-r2 failed. * Call stack: * ebuild.sh, line 1642: Called dyn_unpack * ebuild.sh, line 768: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * fluxbox-0.9.15.1-r2.ebuild, line 61: Called epatch '/usr/portage/x11-wm/f luxbox/files/0.9.15/fluxbox-0.9.15-our-styles-go-over-here.patch' * eutils.eclass, line 161: Called die * * Cannot find $EPATCH_SOURCE! * If you need support, post the topmost build error, and the call stack if rele vant. * A complete build log is located at '/var/tmp/portage/x11-wm/fluxbox-0.9.15.1- r2/temp/build.log'. * Previously, it was fluxbox-0.9.13-our-styles-go-over-here.patch, but now, the ebuilds requires fluxbox-0.9.15-our-styles-go-over-here.patch Thanks ! Reproducible: Always Steps to Reproduce: 1. emerge -va =x11-wm/fluxbox-0.9.15.1-r2
Thanks for this report, I have fixed this. Again. I hope :) Now, is there any reason you're not using the newly stable 1.0_rc3 series? It's much more feature-rich and trendy (and stable!) than the 0.9s Plus once mips stabilizes 1.0_rc3 the 0.9s will be going away.
Thanks ! It's just to test :]
