failed migration to Sequoia

[Nils Breunese]

Artemio González López wrote:

> Yesterday I tried to migrate my Sonoma MacPorts installation to the newly installed Sequoia on a 2019 M1 MacBook Pro 13”. I used the new procedure, i.e.,
> 
> sudo port migrate
> 
> The procedure produced the following errors:
> 
>    Migration finished with errors.
>     The following ports could not be restored:
>      - aspell 
>        Skipped because its dependency db48 failed
>      - emacs 
>        Skipped because its dependency cmake-bootstrap failed
>      - emacs-app 
>        Skipped because its dependency cmake-bootstrap failed
>      - gnuplot 
>        Skipped because its dependency cmake-bootstrap failed
>      - httrack 
>        Skipped because its dependency lzip failed
>      - julia 
>        Skipped because its dependency cmake-bootstrap failed
>      - py311-matplotlib 
>        Skipped because its dependency cmake-bootstrap failed
>      - py311-scipy 
>        Skipped because its dependency cmake-bootstrap failed
>      - py312-matplotlib 
>        Skipped because its dependency cmake-bootstrap failed
>      - py312-scipy 
>        Skipped because its dependency cmake-bootstrap failed
>      - rsync 
>        Skipped because its dependency lz4 failed
>     The following ports could not be fully restored:
>      - py311-jupyter 
>        Skipped because its dependency cmake-bootstrap failed
>        state changed from 'installed' to 'inactive'
>      - py312-jupyter 
>        Skipped because its dependency cmake-bootstrap failed
>        state changed from 'installed' to 'inactive'
>      - py312-jupyterlab 
>        Skipped because its dependency cmake-bootstrap failed
>        state changed from 'installed' to ‘inactive'
> 
> It seems that there is currently a problem with cmake-bootstrap, which affects many ports, and to a lesser extent with db48, lzip and lz4. Does anybody know when these ports are expected to be fixed?

I fixed my issues with cmake-bootstrap on Sequoia by moving the Command Line Tools (/Library/Developer/CommandLineTools) out of the way (rename or remove).

Reinstalling the Command Line Tools might also help, which is something I remember needing to do on every macOS major version upgrade: https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt

Nils.