Unable to execute port: wrong # args: should be "source ?-encoding name? fileName"

[john@…]

Keep getting the following error -

--->  Computing dependencies for ruby
Error: Unable to execute port: wrong # args: should be "source ?-encoding name? fileName"

I have tried multiple ports with the same error.

[jmroot (Joshua Root)]

Did you follow the Migration instructions?

[john@…]

Replying to jmr@…:

Did you follow the Migration instructions?

I uninstalled macports, installed from scratch, then did a self update.

[john@…]

Replying to john@…:

Replying to jmr@…:

Did you follow the Migration instructions?

I uninstalled macports, installed from scratch, then did a self update.

This was my uninstall method.

sudo rm -rf \
    /opt/local \
    /Applications/DarwinPorts \
    /Applications/MacPorts \
    /Library/LaunchDaemons/org.macports.* \
    /Library/Receipts/DarwinPorts*.pkg \
    /Library/Receipts/MacPorts*.pkg \
    /Library/StartupItems/DarwinPortsStartup \
    /Library/Tcl/darwinports1.0 \
    /Library/Tcl/macports1.0 \
    ~/.macports 

I also made sure that I installed the snow leopard version and did a selfupdate.

[ryandesign (Ryan Carsten Schmidt)]

Please remember WikiFormatting.

[ryandesign (Ryan Carsten Schmidt)]

Please show us the debug output -- use the -d switch on whatever command you're executing, for example:

sudo port -d install ruby

Maybe that will shed some light on the problem.

[john@…]

Error log

[john@…]

Replying to ryandesign@…:

Please show us the debug output -- use the -d switch on whatever command you're executing, for example:

sudo port -d install ruby

Maybe that will shed some light on the problem.

I have attached the error log.

One thing of note is that my /opt is a symlink. This has worked in previous versions. Thank you for the help.

[ryandesign (Ryan Carsten Schmidt)]

/opt being a symlink is broken in MacPorts 1.8.0; see #21082. But I haven't seen that problem cause the error message you're seeing.

[john@…]

Replying to ryandesign@…:

/opt being a symlink is broken in MacPorts 1.8.0; see #21082. But I haven't seen that problem cause the error message you're seeing.

Found a work around. Renamed"Mac Ports" "macports"

"Mac Ports" was functioning in the past though.

Thanks again for the help.

[ryandesign (Ryan Carsten Schmidt)]

Oh. I didn't even notice that in the log. Hmm.

[jmroot (Joshua Root)]

#12429