"Unable to open port: can't read "universal_possible": no such variable" after upgrading to 2.7.1

[singalen (Victor Sergienko)]

On upgrade from 2.6.3 to 2.7.1 on MacOS 10.15, I ran port -f uninstall inactive, and got this:

$ sudo port upgrade outdated
Error: Unable to open port: can't read "universal_possible": no such variable
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

Not sure how to diagnose if from here, I couldn't find if it's a problem in a specific package or somewhere else.

--->  Cleaning armadillo
--->  Cleaning arora
--->  Cleaning arowpp
--->  Cleaning arp-scan
Error: Unable to open port: can't read "universal_possible": no such variable

[jmroot (Joshua Root)]

If there's no universal_possible variable, then your base upgrade either didn't happen or was somehow incomplete. (That variable was introduced in 2.7.0.)

[singalen (Victor Sergienko)]

Indeed. Looking for more diagnostics...

$ sudo port selfupdate
Password:
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.6.3 installed,
MacPorts base version 2.7.1 downloaded.
--->  Updating the ports tree
$ echo $?
0
$ sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.6.3 installed,
MacPorts base version 2.7.1 downloaded.
--->  Updating the ports tree

[jmroot (Joshua Root)]

Run sudo port -d selfupdate for full debug output.

[singalen (Victor Sergienko)]

"port -d selfupdate" showed that I had a local source added to Macports. Attached a log. I will clean it up, sorry for confusion.

Maybe it's a reason to give a diagnostic message in this case. Perhaps "Syncing local Git ports tree failed" should be printed on a higher logging level.

[ryandesign (Ryan Carsten Schmidt)]

It doesn't look like you attached the log.

[singalen (Victor Sergienko)]

Sorry, my bad. Attached.

[ryandesign (Ryan Carsten Schmidt)]

Well it says the error is:

DEBUG: system -W /Users/vic/src/amusement/macports-vic: /usr/bin/git pull --rebase --autostash
There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> main

Command failed: /usr/bin/git pull --rebase --autostash
Exit code: 1

I don't know git well enough to advise you on resolving that.

If you want MacPorts to selfupdate without attempting to update your git clone of macports-ports, with which it seems to be having some problem, use:

sudo port selfupdate --no-sync

When you fix whatever the problem is with your ports tree, you can run:

sudo port sync

[singalen (Victor Sergienko)]

Thank you. It was my local project, which didn't have a remote at all.

I admin, it was purely my setup problem. The only thing that macports could do is to print that specific error message even without -d, if possible.

[jmroot (Joshua Root)]

Replying to singalen:

The only thing that macports could do is to print that specific error message even without -d, if possible.

And that was #56549.