The latest beta installer (2.6.8, Sept 2014) appears to not have the exec bit set on the shell script or executables in the MacOS directory, leading to the following error:
2014-10-03 11:38:29.631 com.apple.launchd.peruser.502[172]: (com.bitrock.appinstaller.86976[8800]) Job failed to exec(3) for weird reason: 13
A little chmod a+x fixes this right up.
Thanks!
NBEclipse 2.6.8 installer misconfigured on OS X
Re: NBEclipse 2.6.8 installer misconfigured on OS X
Strange, this is supposed to be set by the installer. I'll verify the version on the web by downloading and testing and likely fixing it today.
Thanks for the report
Thanks for the report
Forrest Stanley
Project Engineer
NetBurner, Inc
NetBurner Learn Articles: http://www.netburner.com/learn
Project Engineer
NetBurner, Inc
NetBurner Learn Articles: http://www.netburner.com/learn
Re: NBEclipse 2.6.8 installer misconfigured on OS X
Hello Ritchie,
Can you specify when exactly you got this error? I just downloaded the installed the release and did not get any problem. Was it when starting the installer, during the install (if so, at what point), or after the installation?
Can you specify when exactly you got this error? I just downloaded the installed the release and did not get any problem. Was it when starting the installer, during the install (if so, at what point), or after the installation?
ritchie wrote:The latest beta installer (2.6.8, Sept 2014) appears to not have the exec bit set on the shell script or executables in the MacOS directory, leading to the following error:
2014-10-03 11:38:29.631 com.apple.launchd.peruser.502[172]: (com.bitrock.appinstaller.86976[8800]) Job failed to exec(3) for weird reason: 13
A little chmod a+x fixes this right up.
Thanks!
Forrest Stanley
Project Engineer
NetBurner, Inc
NetBurner Learn Articles: http://www.netburner.com/learn
Project Engineer
NetBurner, Inc
NetBurner Learn Articles: http://www.netburner.com/learn
Re: NBEclipse 2.6.8 installer misconfigured on OS X
Hi Forrest,
Looks like the problem is related to Keka.app, a multi-format unarchiver for OS X. Maybe it's not preserving metadata bits correctly, though I could have sworn I'd used it to unzip executables correctly in the past. The issue was with the installer app itself, not the product it installed.
If I unzip with Archive Utility.app (the MacOS pre-installed default) everything seems to be ok. Apologies for the mis-report.
Regards,
r.
Looks like the problem is related to Keka.app, a multi-format unarchiver for OS X. Maybe it's not preserving metadata bits correctly, though I could have sworn I'd used it to unzip executables correctly in the past. The issue was with the installer app itself, not the product it installed.
If I unzip with Archive Utility.app (the MacOS pre-installed default) everything seems to be ok. Apologies for the mis-report.
Regards,
r.
Forrest wrote:Hello Ritchie,
Can you specify when exactly you got this error? I just downloaded the installed the release and did not get any problem. Was it when starting the installer, during the install (if so, at what point), or after the installation?
ritchie wrote:The latest beta installer (2.6.8, Sept 2014) appears to not have the exec bit set on the shell script or executables in the MacOS directory, leading to the following error:
2014-10-03 11:38:29.631 com.apple.launchd.peruser.502[172]: (com.bitrock.appinstaller.86976[8800]) Job failed to exec(3) for weird reason: 13
A little chmod a+x fixes this right up.
Thanks!