Opened 3 years ago

Last modified 20 months ago

#62751 closed defect

base: Error: Unable to open port: wrong # args: should be "set varName ?newValue?" on random ports — at Version 1

Reported by: snowflake (Dave Evans) Owned by:
Priority: Normal Milestone:
Component: base Version: 2.6.99
Keywords: Cc:
Port:

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Using macports-base commit changeset:8f4b9e5830479427e1ae09e3d87089c37cb3442b/macports-base 2021/4/17 and the latest version as of now, which is changeset:85d5e10e1fbfc30ad7f7214f2d0b277023213820/macports-base 2021-04-23 12:57:43 +0100 I get this error Error: Unable to open port: wrong # args: should be "set varName ?newValue?"

This is happening on both macOS 10.11.6 and 11.2

Attempting to install the port command with older checkouts of macports-base results in this error: Version number in metadata table is newer than expected

Change History (2)

comment:1 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)

I get this error Error: Unable to open port: wrong # args: should be "set varName ?newValue?"

When doing what? With what port(s)?

Attempting to install the port command with older checkouts of macports-base results in this error: Version number in metadata table is newer than expected

That's expected; you can't use a MacPorts registry with an older version of MacPorts once it has been upgraded to the new format.

Changed 3 years ago by snowflake (Dave Evans)

Attachment: log1.txt​ added

log of sudo port -d upgrade outdated

Note: See TracTickets for help on using tickets.