Happy to report that the migration went smoothly. Just one port installation finished in error (grass, and looking at the port health that was expected, so also qgis3 +grass wasn’t migrated) but that didn’t prevent the migration to complete for all other ports (944 of them).
All this on a MacBook Pro with M1 processor, macOS Sonoma 14.5, Xcode 15.4 and its CLT’s. So, all in all, a very positive experience. Thanks to the MacPorts team! Ciao Franco > On 12 Jun 2024, at 09:46, Franco Vaccari via macports-users > <[email protected]> wrote: > > Dear Josh, > > since your mail caught me a few minutes after updating from Ventura to > Sonoma, and a few seconds before I started to play with MacPorts migration, I > felt obliged to give the migrate command a shot… > > Currently computing dependency order. Will let you know the outcome… > > Ciao > > Franco > >> On 12 Jun 2024, at 09:00, Joshua Root <[email protected]> wrote: >> >> A 'migrate' action has been added to MacPorts base in git on the master >> branch. If you are comfortable with checking out the git repo, installing >> MacPorts from source, running potentially buggy pre-release code, and >> reporting any issues, we would greatly appreciate you giving it a try. >> >> The new action automates all parts of the existing Migration procedure apart >> from updating Xcode and the CLTs. After updating your OS to a new major >> version or transferring to a new machine with a different CPU architecture, >> you should be able to simply run: >> >> sudo port migrate >> >> and MacPorts base will first be rebuilt, and then all ports that need to be >> reinstalled to be compatible with your current system will be. Build >> failures should be handled as gracefully as possible and reported at the end. >> >> Thanks to Umesh Singla for doing the initial work on this feature, and to >> Clemens Lang for doing much of the work of completing and updating the code. >> >> - Josh >
