<div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div><u><b>Context</b></u></div><div><br></div><div>
<div>I am a consultant</div><div>- I have used Macports, but am by no means an expert<br></div><div>- with only SSH-only access,</div><div>- root access (via sudo)<br></div><div>- brought in to build a particular X-windows app on this Mac</div><div> - Motif (libXm) is one missing piece of the puzzle (at least)<br></div><div> - the app builds elsewhere with little trouble, including my ancient AirBook, but I have that in my hot little hands<br></div>
Darwin 16.7.0 ca. June, 2017, x86_64-apple-darwin16.7.0<br></div><div>Xcode version [gcc --version]: Apple LLVM version 9.0.0 (clang-900-0.39.2)<br></div><div>Macports version: 1.9.2, under /opt/local/*/macports/</div><div>- 13 ports total<br></div><div><br></div><div><u><b>So far ...</b></u></div><div><br></div><div>Finally got [selfupdate] to finish by changing rsync_dir in macports.conf</div><div>- per <a href="https://trac.macports.org/ticket/53414" target="_blank">https://trac.macports.org/ticket/53414</a></div><div>- but it still says "base version 1.9.2 installed," and "Warning: No version file found, please rerun selfupdate," and "MacPorts base is probably trunk or a release candidate"<div>- [-d selfupdate] fails to parse 11 of the 13 ports</div>
</div><div><br></div><div>[upgrade outdated] yields "Error: Unable to open port: invalid command name 'port::register_callback'"</div><div>- nothing useful from The Google so far</div><div>- [-d] output below<br></div><div><br></div><div><br></div><div><br></div><div><u><b>My question</b></u></div><div><u><b><br></b></u></div><div>My gut feel is that this is a hopelessly outdated installation of Macports. Rather than shaving the yak and googling as each new problem crops up, is it reasonable to consider removing whatever Macport is there and starting over? I am not even confident that the [uninstall] option would work.</div><div>N.B. [uninstall] is not a solution if the SSH daemon is a Macport, as I would lose access.</div><div><br></div><div>Or do I need someone local to the machine to poke around from the GUI or RDP?</div><div><br></div><div>Thanks in advance,</div><div><br></div><div>Brian Carcich</div><div><br></div><div><br></div><div><u><b>Output of [-d ugrade outdated]</b></u><br></div><div>
<pre style="margin-left:40px">ncursesw (5.8_0 is installed; the port was not found in the port index)
DEBUG: epoch: in tree: 0 installed: 0
DEBUG: gmp 6.2.0_1 exists in the ports tree
DEBUG: gmp 5.0.1_1 is the latest installed
DEBUG: gmp 5.0.1_1 is active
DEBUG: Merging existing variants '' into variants
DEBUG: new fully merged portvariants:
DEBUG: Changing to port directory: /opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/devel/gmp" target="_blank">rsync.macports.org/release/ports/devel/gmp</a>
DEBUG: OS darwin/16.7.0 (Mac OS X 11.2) arch i386
DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided
DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided
DEBUG: Using group file /opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl" target="_blank">rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl</a>
DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf" target="_blank">rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf</a>
DEBUG: Using group file /opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl" target="_blank">rsync.macports.org/release/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl</a>
DEBUG: Using group file /opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/_resources/port1.0/group/cltversion-1.0.tcl" target="_blank">rsync.macports.org/release/ports/_resources/port1.0/group/cltversion-1.0.tcl</a>
DEBUG: invalid command name "port::register_callback"
while executing
"port::register_callback xcode_workaround::xcode_workaround.appy_fix"
(file "/opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl" target="_blank">rsync.macports.org/release/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl</a>" line 132)
invoked from within
"source /opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl" target="_blank">rsync.macports.org/release/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl</a>"
("uplevel" body line 1)
invoked from within
"uplevel "source $groupFile""
(procedure "PortGroup" line 8)
invoked from within
"PortGroup xcode_workaround 1.0"
(file "Portfile" line 5)
invoked from within
"source Portfile"
invoked from within
"$workername eval source Portfile"
(procedure "mportopen" line 49)
invoked from within
"mportopen $porturl [array get interp_options] [array get variations]"
Error: Unable to open port: invalid command name "port::register_callback"
To report a bug, see <<a href="http://guide.macports.org/#project.tickets" target="_blank">http://guide.macports.org/#project.tickets</a>></pre>
</div></div>
</div></div>