failed migration to Sequoia
Joshua Root
jmr at macports.org
Wed Sep 18 15:29:18 UTC 2024
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:
<...>
> 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?
The main problem would be this: <https://trac.macports.org/ticket/70750>
The short version is that the Command Line Tools fail to build C++ code
for some users. We're not yet sure what determines whether they work or
not. If you're affected, uninstalling the CLTs and using Xcode seems to
be an effective workaround.
The migration process uninstalls all ports built for a different OS
version, so unfortunately you won't be able to get back the Sonoma
version of emacs.app using port commands. You would have to restore from
a backup.
Running 'sudo port restore --last' will deactivate all currently
installed ports, and then attempt to activate all ports recorded in the
snapshot that was created during migration, building and installing if
needed. So the only downsides are that it takes some time, and if you
have installed any new ports since the snapshot was created, they may
end up inactive and need to be manually activated.
- Josh
More information about the macports-users
mailing list