failed migration to Sequoia

[Artemio González López]

Hi everybody,

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? Would there be a way of restoring a port (for example, emacs.app, which I use a lot), to its former version before the migration (which worked1)? The migration documentation also mentions to try

sudo port restore —last

to try to reinstall the ports that failed once they are fixed. Is there any downside to this if I try and some of the problematic ports have not been fixed?

Thanks a lot for all the work on MacPorts, which to me is a true gem.

Artemio


Artemio Gonzalez Lopez
artemiog at mac.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20240918/7e7bdda5/attachment.htm>