[MacPorts] #72530: mpstats broken on El Capitan, It's OK on Sequoia

MacPorts noreply at macports.org
Fri May 23 13:26:27 UTC 2025


#72530: mpstats broken on El Capitan, It's OK on Sequoia
------------------------+------------------------
  Reporter:  snowflake  |      Owner:  neverpanic
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.10.99
Resolution:             |   Keywords:
      Port:  mpstats    |
------------------------+------------------------

Old description:

> mpstats has not submitted any stats since 18 April 2025 (according to ls
> -lu )
>
> ```/opt/local/libexec/mpstats show``` displays this:
> {{{
> /opt/local/libexec/mpstats: line 33: package: command not found
> /opt/local/libexec/mpstats: line 37: syntax error near unexpected token
> `}'
> /opt/local/libexec/mpstats: line 37: `}'
> }}}
> Tested on El Capitan.  It is OK on Sequoia

New description:

 mpstats has not submitted any stats since 18 April 2025 (according to ls
 -lu )

 `/opt/local/libexec/mpstats show` displays this:
 {{{
 /opt/local/libexec/mpstats: line 33: package: command not found
 /opt/local/libexec/mpstats: line 37: syntax error near unexpected token
 `}'
 /opt/local/libexec/mpstats: line 37: `}'
 }}}
 Tested on El Capitan.  It is OK on Sequoia

--

Comment (by ryandesign):

 I don't know why that would vary by OS version but it might vary by
 MacPorts version. Do you have the same MacPorts version on both machines?

 mpstats should have /opt/local/libexec/port-tclsh as its shebang line. Can
 you confirm that is the case for you on the machine where you see this
 problem?

 /opt/local/libexec/port-tclsh used to be a symlink to
 /opt/local/libexec/macports/bin/tclsh8.6. Since MacPorts 2.10.6, it has
 been changed to a wrapper script. The change was made on April 18, 2025;
 see comment:ticket:72359:19. Maybe that is a relevant difference between
 your MacPorts installations. Has one of them been updated to the post-
 April 18 code and the other hasn't?

 Please ensure your MacPorts is up to date on both machines. Version
 "2.10.99" just means some version of master, but could be from either
 before or after this base change was made, so please update to the latest
 version of master to see if the problem persists.

-- 
Ticket URL: <https://trac.macports.org/ticket/72530#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list