'daemondo' in MacPorts-2.6.4-10.11-ElCapitan.pkg is of type 'data' upon reinstallation of base pkg

[drfraser (Douglas Fraser)]

Hi,

I needed to reinstall MacPorts and all the installed packages due to messing something up. I followed the reinstallation directions in the wiki and that went fine, but also reinstalled MacPorts base from the package as well just to be safe. I think I uninstalled the ports, then reinstalled the base package first before reinstalling packages.

I then had trouble with trying to do 'sudo port load nginx' - it looked like things ran but nginx never started and I got no error messages from launchctl etc.

I eventually traced the problem to /opt/local/bin/daemondo being not an executable but 'data' according to 'file'. I ended up finding some page about installing the MacPorts_daemondo package to get the file rewritten and so now everything works.

Decompressing MacPorts-2.6.4-10.11-ElCapitan.pkg reveals that the '/opt/local/bin/daemondo' file in this is indeed of type 'data' and not 'Mach-O 64-bit executable x86_64'. There is an 8 byte difference in the size between the 'data' version and the executable version, so I presume there is something wrong with the MacPorts-2.6.4-10.11-ElCapitan package.

I initially installed MacPorts about 10 years ago and have always used selfupdate, never had to or tried reinstalling the pkg - and no problems with daemondo. So I assume the reinstall of the package placed this 'data' file there

Perhaps daemondo gets fixed or set properly somehow and that never happened for me? But that doesn't quite make sense, but I am hardly an expert here. Apologies if I overlooked some step that would have prevented this.

[ryandesign (Ryan Carsten Schmidt)]

Thanks for reporting this problem. I agree with you, there is something wrong with MacPorts-2.6.4-10.11-ElCapitan.pkg. When I extract /opt/local/bin/daemondo from it, the file is all zeroes. We should probably recreate and rerelease this file. Josh, would you have time to do that?

Such a problem is not unprecedented. We previously had a different problem with MacPorts-2.6.3-10.12-Sierra.pkg and had to rerelease it; see #60982.

The installers for older systems don't get as much testing since most users of older systems already installed MacPorts before and update using selfupdate rather than the pkg installer. selfupdate compiles on the user's own system and avoids any problems that might be present in our pkgs.

[ryandesign (Ryan Carsten Schmidt)]

Josh, what do you think?

[jmroot (Joshua Root)]

No sign of this being the case in later versions.