Changes between Initial Version and Version 1 of Ticket #62751


Ignore:
Timestamp:
Apr 25, 2021, 2:40:03 PM (6 months ago)
Author:
ryandesign (Ryan Schmidt)
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #62751 – Description

    initial v1  
    1 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?"```
     1Using 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?"`
    22
    33This is happening on both macOS 10.11.6 and 11.2
    44
    5 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```
     5Attempting to install the port command with older checkouts of macports-base  results in this error: `Version number in metadata table is newer than expected`