Bugzilla Bug 75375

strip mec
mv: cannot stat `me': No such file or directory
>>> Test phase [not enabled]: app-editors/jasspa-microemacs-20040301

>>> Install jasspa-microemacs-20040301 into /var/tmp/portage/jasspa-microemacs-20040301/image/ category app-editors
>>> dobin: making me executable...
>>> dobin: making me32 executable...
install: cannot stat `me32': No such file or directory

!!! ERROR: app-editors/jasspa-microemacs-20040301 failed.


Reproducible: Always
Steps to Reproduce:
1. emerge jasspa-microemacs
2.
3.

Actual Results:  
>>> Install jasspa-microemacs-20040301 into
/var/tmp/portage/jasspa-microemacs-20040301/image/ category app-editors
>>> dobin: making me executable...
>>> dobin: making me32 executable...
install: cannot stat `me32': No such file or directory

!!! ERROR: app-editors/jasspa-microemacs-20040301 failed.


Expected Results:  
emerged ;-)

I did a small research and appears that both available jasspa-microemacs builds
try to do: "mv me m32" (ebuild line 45). But source file "me" is not exists at
this moment. It is created later. But install fails to find "me32" (mv failed to
replace "me32" with non-existant file "me").

I have no idea why this could happen.
Please submit the output of `emerge --info`,
if jasspa-microemacs-20040301-r1.ebuild doesn't install.

I get the same error when emerging with USE="-X". The problem seems to be that
when you build the console-only version, the binary is called "mec" instead of
"me". The ebuild expects it to be called "me" and fails when the file isn't
found.

Sorry, forgot to add: this problem applies to -r1 as well.

Thanks for pointing that. This issue is fixed in -r2.