Go port upgrade went wonky

Kenneth Wolcott kennethwolcott at gmail.com
Sat Aug 1 00:15:27 UTC 2026


Should I force the upgrade?

--->  Cleaning go
--->  Removing work directory for go
--->  Computing dependencies for go.
--->  Deactivating go @1.26.5_0
--->  Cleaning go
--->  Removing work directory for go
--->  Activating go @1.26_0
Error: Failed to activate go: Image error: /opt/local/lib/go already
exists and does not belong to a registered port.  Unable to activate
port go. Use 'port -f activate go' to force the activation.
    while executing
"throw registry::image-error $msg"
    ("foreach" body line 82)
    invoked from within
"foreach file $imagefiles {
                incr progress_step
                _progress update $progress_step $progress_total_steps
                se..."
    invoked from within
"registry::read {
            foreach file $imagefiles {
                incr progress_step
                _progress update $progress_step $progress_t..."
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_go/go/main.log
for details.
Error: Couldn't activate go @1.26_0: 1
Error: Follow https://guide.macports.org/#project.tickets if you
believe there is a bug.
--->  Some of the ports you installed have notes:
  go-1.26 has the following notes:
    Installed as go-1.26 and gofmt-1.26, with GOROOT at
    /opt/local/lib/go-1.26.


More information about the macports-users mailing list